Brotli (Node.js, .NET, Envoy, Python) · CVE-2026-111497 · aka Node2Shell, HTTP2Shell
Brotli decoder RCE
Patch nowIn Node.js, .NET, Envoy, Python. In CISA KEV.
A bug in the Brotli decompressor, built into Node.js, .NET, Envoy and many Python apps, can crash your app, leak memory or possibly run code. It only matters where you decompress Brotli data someone else controls, which is common, and attacks have started. The public exploit only runs code on a deliberately weakened build.
How scary is it?
Are you affected? only if all are true
1A vulnerable Brotli copycommand
Brotli 1.0.3–1.2.0, Node.js below 22.23.4 / 24.22.1 / 26.12.1 (including 20, 23 and 25, which get no fix), .NET 8/9/10, Envoy/Istio, or Python Brotli / brotlicffi below the fix, and PHP for Windows before the 26 Oct rebuilds. On RHEL, Node 22, Node 24 on RHEL 10 and .NET 9/10/11 use the system libbrotli, so update that package too; Node 24 on RHEL 8/9 and .NET 8 bundle their own copy. .NET Framework, Java and pure-JS/Rust ports use other code and aren't affected. process.versions.brotli only shows Node's bundled copy, so check node -v.9,2,5,8,10
node -v
pip show Brotli brotlicffi
dpkg -l | grep -i brotli2You decompress outside Brotli data
Node's fetch() or zlib Brotli APIs, Express 5 request bodies, Python requests/urllib3/aiohttp with a Brotli package installed, .NET HttpClient auto-decompression, ASP.NET Core request decompression or BrotliStream/BrotliDecoder (off by default), PHP's cURL with auto-decompression, or Envoy/Istio with the Brotli decompressor turned on. A bare node:http server doesn't decompress.2,5,9,10
What to do
1Update the runtime
Install the latest safe version for your line (listed below); it also fixes later bugs. Node.js 20, 23 and 25 get no fix, and .NET 8 and 9 reached end of life on 10 Nov 2026. Also: PHP for Windows 8.5.12-1 / 8.4.27-1 / 8.3.36-1 / 8.2.35-1, and Brotli itself 1.0.10 / 1.1.1 / 1.2.1.1,2,5,6,7,10,13,14
Latest safe versions checked 20 Nov
2Rebuild container images
Patching the host doesn't fix copies baked into images. Rebuild, redeploy, and bump lockfile pins.5
3Stopgap: block br request bodies
Reject Content-Encoding: br request bodies at your proxy or WAF. This doesn't cover responses your app fetches.9
This page shows you how to check. It can't tell you you're safe.
Sources (17) and changelog
- google/brotli: fixed releases 21 Oct
- Node.js: October 2026 security releases
- CISA KEV: added 27 Oct 27 Oct
- BleepingComputer: CISA warns of attacks
- Microsoft: .NET out-of-band updates
- Istio: security bulletin 2026-007
- Envoy: GHSA-3wvj-j6qm-62mr
- Red Hat: CVE page
- broccoli2shell.com: preconditions (aggregator)
- PHP: Windows builds rebuilt with Brotli 1.2.1 26 Oct
- Node.js: release index
- Node.js: November 2026 security releases
- .NET 8 release metadata: end of life 10 Nov 2026
- .NET 9 release metadata: end of life 10 Nov 2026
- Envoy: releases
- PyPI: Brotli
- PyPI: brotlicffi
- RHEL bundling corrected (Node 24 on RHEL 8/9 and .NET 8 carry their own copy). .NET 11.0.0 is out; .NET 8 and 9 reached end of life. Safe versions added.
- Review: full Envoy and Node version lists, RHEL system-library note, PHP for Windows, exploit caveat.
- Microsoft: container images must be rebuilt.
- Added to CISA KEV. Verdict raised to Patch now.
- Published.