r/CrowdSec • • Oct 22 '26

general PHP2Shell (CVE-2026-109618 / CVE-2026-109619): If you can’t patch today, install Crowdsec WAF to block the known exploit requests

67 Upvotes

On Wednesday, PHP released emergency updates for two critical vulnerabilities known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Both are rated CVSS 9.2 and can allow unauthenticated remote code execution. Thanks to details that leaked previously to disclosure, the CrowdSec team was able to craft virtual patching rules before the release of the vulnerability.

You can find both WAF rules here:

These rules were live at 10:13 UTC on Oct 21, and the first detection occurred at 10:37 UTC before PHP’s 14:00 UTC release. This detected IP belonged to a Hetzner server in Germany which had never been seen before by CrowdSec. It was later confirmed by numerous other Crowdsec instances.

In the first 23 hours, the rules blocked 2,116 requests from 305 IPs on the CrowdSec Network, more than half of them in bursts of 10+ requests to single servers, which is what a real attempt looks like for this exploit. 

You can find more details about the flagged IPs on the dedicated page of our Live Exploit Tracker: 

If you are already using the WAF,  you can follow this documentation for extra safety. However, on virtual-machines, CrowdSec auto-updates every 24 hours.

No WAF yet? Here is the setup guide: https://doc.crowdsec.net/docs/next/appsec/intro/

Note that patching is the only complete fix; until then, stay safe!

#php2shell


r/CrowdSec • • Jun 14 '26

general Apparently somebody just gave up

Post image
61 Upvotes

had to use custom blocklists but good riddance
thanks crowdsec

UPDATE: they are back :[


r/CrowdSec • • Sep 28 '26

general GeoMetrikks v0.19.0 bot-detection support, ban map and more CrowdSec stuff

Post image
53 Upvotes

With the new bot detection release I thought I'd share some new feats I've added

For those who hasn't seen it here is the tldr of what the app is:

GeoMetrikks is a real-time nginx/traefik/caddy access log ingestion and geo-location tracking service built with Litestar. It parses access logs, performs GeoIP lookups, and stores geo-events and access logs in PostgreSQL with TimeScaleDB/PostGIS extensions. It can also integrate with CrowdSec.

tltldr: shove web server logs into db, make app display data and numbers, watch pretty colors on map.

Some of the newer stuff:

- CrowdSec 1.8 bot-detection alerts - inspect rejected browser

challenges, including scores, rejection reasons and

fingerprint details, even when there's no ban.

- More detailed alerts - see the paths, user agents and events

CrowdSec collected, and jump from a decision to the alert

behind it.

- Ban IP ranges or create captcha decisions from the UI,

with custom durations and reasons.

- A dedicated banned-IP map view, with links into each IP's

activity and current decisions.

- Generate abuse reports for an IP or ASN, with log excerpts

and CrowdSec detections. Export as text or CSV, and look up

the network's abuse contact.

- Links straight to CrowdSec CTI and the relevant Hub scenario.

The idea is to make it easier to go from "why is this IP banned?"

to seeing what it was actually doing, without jumping between

a bunch of tools.

https://geometrikks.dev

https://github.com/GilbN/geometrikks

Would be interested to hear what else you'd find useful,

especially from anyone trying the new bot-detection stuff.


r/CrowdSec • • Sep 01 '26

general CrowdSec 1.8 : Bot detection and more

51 Upvotes

Hello 🦙

We released CrowdSec 1.8 yesterday, and it comes with bot detection for the WAF amongst other things. You can find more here : https://www.crowdsec.net/blog/crowdsec-1-8-waf-bot-detection-kubernetes

You can find bot detection doc here.


r/CrowdSec • • 12d ago

general My server is sleeping like Baby, thanks to CrowdSec

50 Upvotes

Lately, my server was going down every few hours due to bot traffic, I tried fail2ban initially which was helpful however the problem - I need to always depend on Rate Limit and by that time, some attacks were really bad and hard to catch.

After 20 days of facing same, I deployed CrowdSec with basic bouncer rule.

apt install -y crowdsec

with

apt install -y crowdsec-firewall-bouncer-nftables

No more cacophony from uptime monitoring services. 😂

Initially I was very afraid that this might be really technical and hard to understand but I figured out in just 1 hour, successfully managed to deploy and test with cscli metrics command.


r/CrowdSec • • 25d ago

general PHP2Shell after five days on the CrowdSec network: still no mass exploitation

45 Upvotes

Hey that's Matt from the CrowdSec data team and I am sharing what the network saw in the first five days of PHP2Shell.

On the timeline: The details of the vulnerability leaked on the 20th, the FOSS team managed to write a vpatch rule and merged it on the Hub at 10:13 UTC on the 21st. A sensor blocked the first request at 10:37. When the CVEs were published at 13:34, 17 IPs had already been blocked, and 18 by the time PHP released the fix.

From October 21 to 25 (UTC), 1,730 sensors blocked requests from 1,187 IPs. Sorted by when each IP first showed up:

- Wednesday afternoon: 72 IPs probing.

- Overnight: 238 more, mostly going for the session upload route (CVE-2026-109619), the easier of the two.

- Thursday 10:00 to 15:00: 405 new IPs in five hours, 72% of which had attacked React2Shell in the previous 90 days. One known fleet switching targets.

- Thursday evening to Sunday: about 130 new IPs a day. There was no second wave.

My read on why it stays quiet: there is no public exploit that works reliably on a default PHP install and can be used at scale. The working exploits are still confidential and used only when the outcomes are certain. This aligned with what we show in the traffic analysis. Half the sources sent a single request in five days, which is unlikely to go through given the nature of the exploit.

You can find more details including charts and complete timeline description in the full write-up: PHP2Shell, five days in

Live Exploit Tracker can also be used to monitor the evolution of the threat for : CVE-2026-109619

Found this post useful? Let us know with a comment or an upvote. If your alerts show something different, don't hesitate to share it below with the community, this is always something we love hearing about.


r/CrowdSec • • Sep 17 '26

general CrowdSec Update: Source Code Leak

42 Upvotes

An update from Crowdsec via e-mail today:

Hello,

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. We do not confirm any “other file contained” or “internal development material”, since all the code is published in these repositories. The API related information is the token used by the CI/CD component itself. (see below)

No client data, login/password, name, organization, or anything else was leaked, and CrowdSec doesn’t store PII or client logs; the impact is limited to CrowdSec. Our team quickly hunted for any token, credential, or sensitive leak that could enable lateral movement but found none so far.

The code contained in these private repositories has value but cannot really harm CrowdSec, since our efficiency depends on our network effect and size, which code alone can't replicate. We regularly audited the SaaS source code, and its leakage shouldn’t pose an immediate threat either. Most of the leaked code has evolved significantly over those four months, but we will closely monitor for any abnormal activity. Also, using it outside of CrowdSec seems unlikely because it only interacts with our data and tools and cannot really be leveraged in another context.

We will keep you updated as we continue investigating, but the TanStack compromise is very likely to have been the leak vector (more about it here), as in the case of the Mistral AI case. This component was used in our organization in May and appears to have been backdoored to extract an API key with authorization to read the private codebase. The leak was only exploitable during a short timeframe in May 2026.

We nevertheless immediately rotated all required tokens & credentials to prevent further incidents.

The team would like to thank Fuites Infos for their timely, professional outreach in reporting the issue.

If you have any questions or concerns, please contact us through our Discord channel or at [email protected].

Thank you for your continued trust,

The CrowdSec Team


r/CrowdSec • • Feb 12 '25

general Would love a $5-10 /mo option - anything to bridge the gap between free and $31/mo

41 Upvotes

This could entail, for instance, a lite-premium license option providing access to more community block lists - or perhaps a few silver / gold lists? Just a thought!


r/CrowdSec • • Mar 26 '26

general Am I missing something here, or is this a genuine horrifically bad address?

Post image
39 Upvotes

For the first time that I’ve noticed, I found my OPNsense box displaying a blocked Crowdsec address (77.169.127.181) going OUT of the network (WAN), not in. So I plugged it into the CTI part of my Crowdsec portal. Was not expecting this!

Edit: OPNsense shows it continuously being reached every 5mins… it’s still being attempted as I type?!

SOLVED! See response by Q-Feeds below.


r/CrowdSec • • Nov 18 '25

Self-Hosted Security Made Simple: Strengthen Your Pangolin Setup with CrowdSec

Thumbnail
app.livestorm.co
37 Upvotes

Learn how to combine Pangolin’s self-hosted, tunneled reverse proxy with CrowdSec’s collaborative intrusion prevention system to build a resilient, privacy-preserving web defense.

In this live session, you’ll discover how Pangolin gives you full control of your network traffic and infrastructure, while CrowdSec adds real-time threat detection and automated blocking powered by community-driven intelligence.

We’ll explore real-world use cases, integration benefits, and how to deploy Pangolin with CrowdSec preconfigured for seamless protection.


r/CrowdSec • • Dec 09 '25

CVE-2025-55182 known as React2Shell Free Blocklist

Thumbnail
app.crowdsec.net
36 Upvotes

With the React2Shell vulnerability (CVE-2025-55182) now being actively exploited in the wild, some organizations may struggle to deploy patches quickly enough across all environments.

To help reduce exposure, CrowdSec is releasing a free blocklist that tracks and blocks IPs currently involved in large-scale exploitation attempts of this CVE.

  • Continuously updated list of malicious IPs exploiting CVE-2025-55182

  • Available through the Console Integrations or can be subscribed at the engine level.

  • Compatible with firewalls, proxies, and WAFs

Note:

This blocklist is not a replacement for patching. You should still prioritize applying the vendor’s fix. However, pairing the blocklist with CrowdSec’s WAF or existing perimeter defenses can significantly reduce risk from unpatched systems and local exploitation attempts.


r/CrowdSec • • Feb 24 '26

general Introducing CrowdSec Monitor, a REST API and iOS client for CrowdSec

35 Upvotes

Hi everyone. I have created a REST API and an iOS app for CrowdSec. I decided to do this because I wanted an easy way to check the alerts and decisions from my phone, without using a web app (I hate using web apps on mobile devices). Both parts are completely free and open source.

CrowdSec Monitor API

The API is built with Node.js and Express.js, and a Docker image is available to deploy it. This API offers a built in auth method, but it's a very basic one. I recommend putting in front a reverse proxy with a basic auth system, or using a third party identity provider.

GitHub Repository

CrowdSec Monitor iOS

The app is a native app built with SwiftUI to achieve good performance and an UI that follows Apple's design guidelines.

GitHub Repisotory, App Store

CrowdSec Monitor Android

I have created recently the Android version. For now it's on closed testing until 12 testers test the app for 14 days (thanks Google), after that it will be released on the production channel for everyone. If you want to become a tester here you have the instructions.

What's next?

This is the first release, with just the basic stuff. There will come new features, and here's a list of what I have in mind:

  • More charts and QOL improvements for the mobile app

  • Widgets for the Home Screen on the native app

  • New menu to manage the whitelists

  • Ability to generate PDF reports about an alert to save them or to share with someone else

  • A notifications system, where the user can configure to be notified when an alert with a certain scenario enters. The notification options will be via email or using the ntfy service

Other features (need to study if it's possible)

  • Full list of IPs that are currently banned. For this to be possible, the API will have to be registered as a bouncer in CrowdSec

I hope you find this project interesting and useful. I have just released it so you can expect some bugs. You can open issues on the respective repositories. Also, feature requests are welcome.


r/CrowdSec • • Feb 26 '26

general CrowdSec Has a Public Roadmap (and you may vote and contribute)

Thumbnail roadmap.crowdsec.net
31 Upvotes

Hello Alpacas - It has been released a while ago, and yet it seems to me this has fallen under the radar: Crowdsec has a public roadmap website

On this page, you can find the next features plan for the Quarter, vote for the most useful ones, and even suggest your ideas. Contributions are really welcome!

https://roadmap.crowdsec.net/


r/CrowdSec • • 24d ago

general CrowdSec 1.8.2, Apache Bouncer and webinar

29 Upvotes

Hello !

Despite php2shell, the internet didn’t end, so we released more stuff:

CrowdSec 1.8.2 brings very significant improvements to the bot detection feature, allowing us to ship custom bot detection via the hub, and users to craft their own. Bot Hunting is a cat and mouse game, so we wanted to be sure to decorrelate detection and scoring from CrowdSec releases. We thus shipped some new detection methods and signals that we found to detect common “stealth browsers”. We also shipped various performance improvements for both the WAF, the Bot Challenge and the Log Processing features. You can read more in the release note.

Apache CrowdSec Bouncer finally got some love. This total revamp of the existing bouncer brings support for the Web Application Firewall and the Bot Detection feature natively to apache, alongside with stream support. It was long overdue, and php2shell pushed us to speedrun the module’s release. Read more here.

Also, u/bl0tus and I are running a webinar tomorrow afternoon (29/10) at 4pm CET on the new bot detection feature, we will showcase new bot detection features and signals, so come join us : https://www.youtube.com/live/rHKs3yAquQo

Stay safe 🦙


r/CrowdSec • • May 15 '25

general New Threat Intelligence tool

29 Upvotes

Hey everyone,

I just published a new article about a tool we recently released at CrowdSec: IPDEX, a CLI-based IP reputation index that plugs into our CTI API.

It's lightweight, open source, and helps you quickly check the reputation of IP addresses - either one by one or in bulk. You can also scan logs, run search queries, and store results locally for later analysis.

If you're into open source threat intel or just want to get quick insights into suspicious IPs, I'd love your thoughts on it!

Article: https://www.crowdsec.net/blog/introducing-crowdsec-ipdex
GitHub: https://github.com/crowdsecurity/ipdex

Happy to answer any questions or hear your feedback.


r/CrowdSec • • Sep 10 '26

general Bot Detection with Crowdsec - Introduction Blog Post

Thumbnail
crowdsec.net
27 Upvotes

Find out how to setup the Bot Detection and how it compares with other existing systems

If you have tried it we would love to hear from you! Please share your experience in this thread


r/CrowdSec • • May 25 '26

general CrowdSec skill - because life is too short to read docs!

Thumbnail github.com
27 Upvotes

We just published the CrowdSec skill! It can already be used with Claude (web/code), Codex etc.

Very concretely, it provides you with an actionable answer to questions and requests such as:

  • “Why isn’t my crowdsec instance detecting attacks on my nginx server ?”

  • “Set up the crowdsec WAF on my Traefik server”

Once an internal experiment, it yielded very convincing results, so now it’s time to put it into our users’ hands.

Documentation is really hard. Hard to read, because it’s hard to write, so hard that it’s not very far from “naming things” hard. While it would be easy to dismiss it as “people don’t read documentation”, it would be unfair.

Thus, this skill aims to be the CrowdSec handbook for LLMs, and I believe it can really help our users set up CrowdSec, debug it, and improve their existing setups.

The development process was funny and a good example of a feedback loop and self-correction:

  • Once I had a detailed plan and structure of what the skill should cover or exclude, I dedicated an EC2 for Claude to test every setup and scenario. It then deployed various web servers, bouncers, and ecosystems (Docker, Kind, etc.) to validate and self-correct the skill’s content.

  • Later, we moved on to present Claude with deliberately broken and misconfigured setups that reflect the most common issues we’re seeing. Again, once it had fixed the setup and identified the root cause (sometimes laboriously), session content was used to amend the plan.

  • Last but not least, we extracted raw content from over a thousand threads in the Discord support channel to identify recurring topics and, using our test bed, try to reproduce the initial issue and ensure the skill contained the relevant pointers to fix it.

Stay safe! And as usual, don’t hesitate to reach out for feedback, suggestions or a rant 😄


r/CrowdSec • • 8d ago

general Pricing for homelabs

25 Upvotes

I like Crowdsec and wouldn't mind paying for it, but $29/mo. seems a bit steep, really. Are you thinking about making a special offer for homelabs?


r/CrowdSec • • Feb 06 '26

general Home Assistant plugin

25 Upvotes

Hey! I use crowdsec at home and also love my home assistant home automation stuff, so I built an integration that lets you pull info from your crowdsec instance.

https://github.com/dewgenenny/crowdsec_ha

Sorry if not interesting, thought I'd share just in case there was anyone else out there that uses both HA and Crowdsec :)


r/CrowdSec • • 3d ago

general Java4Shell : Virtual patching rules

23 Upvotes

Hello,

As people are reaching out, we just published a Java4Shell virtual patching rule for CrowdSec's WAF:

https://app.crowdsec.net/hub/author/crowdsecurity/waf-rules/vpatch-CVE-2026-114938

As usual, it is part of the virtual patching collection, so it will come automatically in the next update.

See the WAF setup guide if you're late to the party.

Stay safe 🦙


r/CrowdSec • • Apr 16 '23

The Crowdsec documentation is awful…

22 Upvotes

Im going to try and stay constructive and not rant but i cant make any promises. For any installation outside of a single server install the documentation is just bad.

All around it is very hard to follow along with. Most documentation follows some kind of structure like;

Explanation
Command
Explanation 
Command

Or reversed, it doesnt really matter, but all throughout the docs for crowdsec the structure is just kind of random which makes it very difficult to figure out which explanation goes with which command and vise versa.

Several times I found myself reading the same page over and over again and still not knowing which machine I’m supposed to run the command on, or which parts of the command I need to substitute with my own info and which parts to just copy.

To make the previous issue even worse almost any time an IP address is mentioned there is no explanation at all for what the IP is for.

For example, in the guide for a multi-server installation the IP 10.0.0.1 is used but with no indication of what the address is. is that the IP of the local machine? Is it the ip of the remote machine? Is it something else entirely and does actually need to stay 10.0.0.1?

When trying to figure out how to connect an agent to a lapi on another machine some parts of the docs have you run a command where you provide the name of the agent, others don’t, and then others have you generate a key…which is it? Will any one of them work? And why don’t any of them have decent explanations of what the command is actually doing?

Why does the official multi server guide have you comment out the listen address in config.yaml but no other guides do?

Why do most pages and guides reference acquis.yaml but other’s reference individual files for each log file? Speaking of acquis.yaml, why do I have to use google to find the documentation for how to set it up?

Why is there no documentation on tools you can use to actually test if any of this is even working?

Look I don’t want to just keep ranting, but for such an awesome project the docs are just plain awful, they are confusing, hard to follow, lack context, and even contradict themselves.

I spent an entire week trying to setup 2 docker agents, with a lapi on an ubuntu machine with 1 bouncer…I finally got the Ubuntu machine working correctly after hours of trial and error from piecing together info from multiple sources. The 2 docker agents…that never happened. I ended up using Syncthing to just sync the various log files to the lapi server and calling it a day. Atleast I managed to get it working.


r/CrowdSec • • Sep 02 '25

general CrowdSec v1.7 just released! Self hosted IDS/IPS/WAF

Thumbnail
reddit.com
21 Upvotes

r/CrowdSec • • 7d ago

general CrowdSec Escalation Controller

Post image
20 Upvotes

Hey everyone,

I've been working on cs-escalation-controller, an open-source tool that extends CrowdSec bans for repeat offenders.

The idea is straightforward. When an IP comes back after a ban and gets banned again, its next ban gets longer. By default, durations start at 4 hours and double with each offense, up to 30 days. Those values are configurable.

It connects to CrowdSec's Local API and keeps persistent per-IP history, so restarting the controller doesn't lose track of previous offenses. Overlapping alerts during the same ban count as one offense, and it preserves existing bans that are already longer than the calculated duration.

History resets after a configurable quiet period, with time spent banned excluded from that period. You can also exclude specific scenarios from escalation.

It runs as a standalone binary or a Docker container. Dry-run mode is enabled by default, so you can see what it would do before letting it create decisions.

Code and configuration: https://github.com/crazy-max/cs-escalation-controller

I'd be interested in feedback from you, especially on how you handle repeat offenders today and what escalation or reset settings make sense for your setups.


r/CrowdSec • • Oct 04 '23

⚠️ Vulnerability Alert ⚠️

20 Upvotes

We are aware of the the new Linux vulnerability (CVE-2023-4911) named Looney Tunables which was found in the GNU C library's dynamic loader. Our team is working on a Scenario to help users detect and block exploitation attempts.

More information to come soon.