The short version
- One bug, many names: Node2Shell, HTTP2Shell, Python2Shell and Broccoli2Shell all mean CVE-2026-111497 (CVSS 4.0 9.2 from the CNA; Node.js rates it High).
- Fixed in Node.js 22.23.4, 24.22.1 and 26.12.1. Node 18, 20, 23 and 25 are end-of-life and get no fix.
- Inbound exposure: a request body with
Content-Encoding: brreaching a parser that inflates it. Express 5 and body-parser 2.x do this by default. - Outbound exposure:
fetch()decodes a Brotli response automatically, so a malicious or compromised server you call can send the payload. Upgrading is the only fix for fetch. - Don't check
process.versions.brotli: it still says 1.2.0 after patching. Check the Node version, and restart the process.
1. What Node2Shell is
Brotli is the compression format behind Content-Encoding: br. Node.js doesn't implement it in JavaScript; it bundles Google's C decoder inside its zlib module. CVE-2026-111497 is a bug in that decoder.
A crafted Brotli stream declares one type of data block and then asks the decoder to switch block types in a way that should stop it with an error. The vulnerable decoder ignores the error and keeps going, writing past the end of its buffer. Depending on the build and the heap layout, that's a crash, a memory leak, or code execution. No authentication is involved: the decoder runs on whatever data it's handed.
One detail worth knowing: the fix landed upstream in Brotli on 27 February 2026 without a security label. It was another eight months before the CVE and the runtime releases followed. Silent fixes like that are one more reason to track runtimes, not just the CVE feed.
2. Node2Shell, HTTP2Shell, Python2Shell, Broccoli2Shell
The first write-ups were about Node.js, hence Node2Shell. Within two days Python was linked to the same bug, then Bun, .NET, Envoy and Istio, and the name broadened to HTTP2Shell, because anything that decompresses HTTP bodies can reach the decoder. Broccoli2Shell is the pun on Brotli. All of them mean CVE-2026-111497. Despite the name, HTTP2Shell has nothing to do with the HTTP/2 protocol.
For the Python side (requests, urllib3, httpx, aiohttp), see Py2Shell.
3. Am I affected?
Two questions: is your runtime unpatched, and does untrusted Brotli data reach the decoder?
| Runtime or proxy | Fixed in | Notes |
|---|---|---|
| Node.js | 22.23.4, 24.22.1, 26.12.1 | 18, 20, 23 and 25 are end-of-life: no fix |
| Bun | 1.4.4 | Affected from 1.0.21; rebuild compiled executables |
| Brotli C library | 1.0.10, 1.1.1, 1.2.1 | Affected 1.0.3 to 1.2.0 |
| .NET 8, 9, 10 | 8.0.33, 9.0.22, 10.0.14 | Decompression is off by default; .NET Framework not affected |
| Envoy, Istio | Envoy 1.40.0, 1.39.3, 1.38.6, 1.37.8; Istio 1.31.2, 1.30.6, 1.29.9 | Only where the Brotli decompressor filter is configured |
Inbound: an attacker sends a request body with Content-Encoding: br. Express 5 with body-parser 2.x inflates it by default before your route runs. A bare http server that doesn't decode bodies isn't exposed this way.
Outbound: your code calls a server that returns a Brotli response, and fetch() decodes it automatically. That covers webhooks you deliver, URL previews, scrapers, and any third-party API that's compromised. Removing br from Accept-Encoding doesn't help, because a malicious server can send Brotli anyway.
Files: Brotli also sits inside WOFF2 fonts, some PDFs and Parquet files, so processing uploads can reach it too.
4. What to upgrade, and the workarounds
- Upgrade Node and restart. Bump the
FROM node:…tag to a fixed release, rebuild, redeploy. A running process keeps the old decoder until it restarts. - Check the right number.
process.versions.brotlireports 1.2.0 even on patched builds. Checknode --versionagainst the table. - Inbound stopgap: reject any request whose
Content-Encodingcontainsbrin middleware placed before the body parsers, or setinflate: falseon them. CDN and WAF rules, including Cloudflare's emergency release on 25 October 2026, cover inbound traffic only. - Outbound: there is no workaround for
fetch()short of upgrading. Forcurl, drop--compressed. - Proxies: on Envoy and Istio, remove the Brotli decompressor filter and confirm it's gone from the live config, not just the YAML.
5. Exploitation status
This is where sources disagree, so here's the spread rather than one answer. CISA's assessment on 23 October 2026 recorded no exploitation, and Red Hat reported that the public proof-of-concept reached code execution only on deliberately weakened builds. Imperva reported running attacker code on a stock Node.js 24.22.0 arm64 build after several attempts. Later reports from ELLIO described exploit traffic in the wild, and Brandefense reported a CISA KEV listing on 27 October.
For planning purposes it doesn't matter much: a public crash exploit exists, code execution has been shown on at least one stock build, and the fix is a minor version bump. Patch it as exploited.
6. How Compass helps
Compass, our open-source (Apache 2.0) operations agent for AWS, does two things for a bug like this one.
Before: find every Node, open the fix
- The patch captain reads OSV, the CVE list, CISA KEV, EPSS, the npm advisories and the distro trackers every hour, and matches them every fifteen minutes against what your account runs:
node:images in ECS task definitions and Dockerfiles, and the packages inpackage.jsonand lockfiles. - Each finding names the repository and file, the workloads that run what it builds, and whether any of them faces the internet. That's the answer to "where do we run an unpatched Node?", which is usually the slow part.
- For a critical, internet-facing finding with a plain version bump, it opens one fix pull request per repository without a click (
node:24.22.0-slimtonode:24.22.1-slim), then reads CI, the image build and an optional staging canary. End-of-life lines (Node 18, 20) need a major upgrade, so those wait in the inbox with the reason stated. It never merges.
During: honeytokens for the window before the patch
- If someone does get code execution in a Node process, their first move is almost always reading the environment. Compass plants decoy AWS keys and database logins (as Terraform pull requests you merge) for you to put next to the real variables.
- When a decoy is used, CloudTrail and EventBridge deliver the event, and Compass opens an incident that names the one task definition the decoy came from. With your policy's permission it restarts that ECS task or deactivates the key, with a snapshot, verification, an audit entry and a rollback.
What it doesn't do: block the malicious request, or see an attacker who never touches a decoy. Restarting removes a foothold but doesn't patch the decoder; the pull request does. That combination contained our PHP2Shell incident in under two minutes. More about Compass.
7. FAQ
What is Node2Shell?
Node2Shell is the nickname for CVE-2026-111497, an out-of-bounds write in the Brotli decompression library that Node.js bundles. Crafted Brotli-compressed data makes the decoder write past the end of its buffer, which can crash the process, leak memory, or in some builds lead to code execution. Node.js released fixes on 21 October 2026.
Is HTTP2Shell the same as Node2Shell?
Yes. HTTP2Shell, Node2Shell, Python2Shell and Broccoli2Shell are all names for CVE-2026-111497. The bug is in the Brotli decoder, so every runtime and proxy that ships that decoder and decodes untrusted input is affected, which is why the name drifted from Node to HTTP in general. It has nothing to do with the HTTP/2 protocol.
Which Node.js versions fix CVE-2026-111497?
Node.js 22.23.4, 24.22.1 and 26.12.1. Node 18, 20, 23 and 25 are end-of-life and received no fix, so move to a supported line. Bun fixed it in 1.4.4; compiled Bun executables must be rebuilt.
Is my Express app vulnerable to Node2Shell?
Express 5 with body-parser 2.x inflates request bodies with Content-Encoding: br by default, so an unpatched Express 5 app parsing JSON or form bodies is exposed to inbound attacks. Upgrade Node. Until then, reject requests whose Content-Encoding contains br before any body parser runs, or set inflate: false on the parsers. A plain Node http server that doesn't decode bodies isn't exposed inbound.
How do I check whether my Node.js is patched?
Check the Node version with node --version, not process.versions.brotli, which still reports 1.2.0 on patched builds. Then make sure the running process was restarted after the upgrade: a long-running Node process keeps the old decoder in memory until it restarts. For containers, check the image tag or digest your service actually runs.
Is Node2Shell exploited in the wild?
Reports disagree. CISA's assessment on 23 October 2026 recorded no exploitation, and Red Hat reported no reliable public exploit for code execution, while later reports described exploit traffic and a CISA KEV listing on 27 October. Check the KEV catalogue directly, and patch as if it is exploited: a public proof-of-concept for the crash exists.
Written by Ilia Dubovskii, founder of Beamreach. Versions, dates and exploitation reports were checked against Node.js, Phoenix Security, Akamai, Sysdig and Brandefense publications on 17 November 2026. Reports on exploitation disagree; check the Node.js security release notes and CISA KEV before relying on a status here.
Related: Py2Shell: the same bug in Python · React2Shell (CVE-2025-55182) · The *2Shell vulnerabilities, 2021 to 2026 · AWS canary credentials · One Fake Password Is Worth More Than 10,000 Alerts (talk)
Beamreach