Broccoli2Shell
A critical flaw in the compression code built into Node.js, Bun and Python can let attackers run code on your servers. Most cloud setups run something affected.
The risk
Data and secrets stolen from your servers
- Attackers running their own code on your servers
- Proxies that see all your traffic compromised (Envoy, Istio)
- Services crashed and taken offline
- Triggered by a single crafted, compressed request
Who is affected
Node.js
Bun
Python
Next.js
Fix it yourself.
- Find where it runs. List your Node.js, Bun and Python services and proxies.
- Upgrade and rebuild. Update to the fixed versions, rebuild containers, redeploy.
- Restart everything. Running processes keep the old code until restarted.
CVE-2026-111497 · Critical
| Software | Vulnerable | Fixed in |
|---|---|---|
| Node.js | unpatched 22.x, 24.x, 26.x | 22.23.4 · 24.22.1 · 26.12.1 |
| Bun | 1.0.21 – 1.4.3 | 1.4.4 |
| Google Brotli / Python Brotli | 1.0.3 – 1.2.0 | 1.0.10 · 1.1.1 · 1.2.1 |
| Python brotlicffi | 1.0.3 – 1.2.0.x | 1.2.1.0 |
| Envoy Proxy | 1.36.11, 1.37.7, 1.38.5, 1.39.2 | 1.36.12 · 1.37.8 · 1.38.6 · 1.39.3 · 1.40.0 |
| Istio | 1.29.0–1.29.8 · 1.30.0–1.30.5 · 1.31.0–1.31.1 | 1.29.9 · 1.30.6 · 1.31.2 |
| Go: andybalholm/brotli | before v1.2.7 | v1.2.7 |
An out-of-bounds write in the Brotli decoder (also called Node2Shell or HTTP2Shell). Reported by researchers credited to OpenAI Codex Security. Exploitation was demonstrated against unpatched Node.js. If you can't patch yet, temporarily reject requests with Content-Encoding: br. Wiz reports 82% of cloud environments have publicly exposed Node.js.
Sources: Wiz: Broccoli2Shell. Last updated October 26, 2026.
A client who dealt with this.
"LastGap detected Broccoli2Shell on our production Next.js site before we even knew it existed. They walked us through the exposure and patched it."

Questions
Is my Node.js or Next.js app affected?
Unpatched Node.js 22.x, 24.x and 26.x releases are affected. Upgrade to 22.23.4, 24.22.1 or 26.12.1, rebuild and redeploy.
Is Broccoli2Shell being exploited?
Researchers have demonstrated working exploitation against unpatched Node.js. As of October 25, 2026, no confirmed attacks in the wild had been reported.
Is updating my server enough?
Not always. Containers and lockfiles can keep shipping the old code. Rebuild, redeploy and restart.