CrowdSec Source Code Leak
CrowdSec BlogAnnouncementSep 17, 2026CrowdSec Statement: Source Code Exposure in May 2026 On September 16, CrowdSec was informed of a source code leak involving our GitHub repository, which occurred in May 2026. CrowdSec source code consists of two parts: a private one and another that hosts our Free Open Source Software (i.e., the Security Engine), which is public by design and therefore out of scope. The private part, though, contains the source code for our SaaS console, some AWS Cloud routines, some connectors, and automations.
- ▪CrowdSec BlogAnnouncementSep 17, 2026CrowdSec Statement: Source Code Exposure in May 2026 On September 16, CrowdSec was informed of a source code leak involving our GitHub repository, which occurred in May 2026.
- ▪CrowdSec source code consists of two parts: a private one and another that hosts our Free Open Source Software (i.e., the Security Engine), which is public by design and therefore out of scope.
- ▪The private part, though, contains the source code for our SaaS console, some AWS Cloud routines, some connectors, and automations.
Hacker News (Front Page) files mainly under programming. We currently carry 1,764 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Crowdsec |
| Canonical URL | https://www.crowdsec.net/blog/crowdsec-statement-source-code-exposure |
| Publication time | Thu, 17 Sep 2026 15:34:01 +0000 |
| Retrieval time | 2026-09-17T16:13:44.272Z |
| Last seen | 2026-09-17T16:13:44.272Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | uxfBpQC_FJkn · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
CrowdSec BlogAnnouncementSep 17, 2026CrowdSec Statement: Source Code Exposure in May 2026 On September 16, CrowdSec was informed of a source code leak involving our GitHub repository, which occurred in May 2026. Our team verified and confirmed the report. CrowdSec source code consists of two parts: a private one and another that hosts our Free Open Source Software (i.e., the Security Engine), which is public by design and therefore out of scope. The private part, though, contains the source code for our SaaS console, some AWS Cloud routines, some connectors, and automations. The news headline claiming 300 different repositories is accurate (when you include the 130+ public ones), though that number mostly reflects the code’s subdivision rather than a specific volume.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Crowdsec.
Discussion
0 commentsMore from Crowdsec
