“We don’t even use Brotli.” That’s a reasonable first reaction. Most business owners have never heard of it.
Here is the catch: you probably do use it, just not on purpose.
Brotli is a compression format Google created to make web pages and data smaller and faster to send. It’s built into browsers, web servers, programming languages and cloud tools, usually several layers below anything you would ever see. That’s what makes this flaw worth understanding, and also why a lot of what’s circulating on social media about it overshoots the facts.
What actually happened
On October 21, Node.js shipped security releases that included a fix for a flaw in the Brotli decoder it bundles. Some coverage nicknamed it Node2Shell, and we mentioned it briefly in our PHP2Shell breakdown. On October 22, Google published the formal record, CVE-2026-111497, confirming the bug is in Google’s own Brotli library, not just in Node.js.
According to Node.js, malformed compressed data could push the decoder into an invalid state, after which it kept writing past the end of a small internal buffer. An attacker who can get an application to decompress Brotli data they control can corrupt that program’s memory. The possible results are a crash, a leak of whatever was in memory, or, in some setups, running the attacker’s own code.
Google rates it 9.2 out of 10, Critical. Red Hat scores it 8.1 and rates it Important, noting that reliable code execution is harder on hardened systems. Node.js rates it High. The scores differ, but every one of them says “patch this.”
What’s confirmed, and what isn’t
Posts calling this “HTTP2Shell” and warning that every app is now open to takeover are moving faster than the evidence. Here is where things stand as of October 24:
- Confirmed affected: Google Brotli 1.0.3 through 1.2.0. Node.js 22, 24 and 26; end-of-life Node.js lines won’t get a fix. Envoy proxy deployments that have its Brotli decompressor configured. Linux distributions that ship the library.
- Fixes available: Brotli 1.0.10, 1.1.1 and 1.2.1. Node.js 22.23.4, 24.22.1 and 26.12.1. Envoy 1.36.12, 1.37.8, 1.38.6, 1.39.3 and 1.40.0. Debian has released updated packages, Red Hat has begun shipping fixes, and the Python Brotli package was updated to 1.2.1 on October 22.
- Proven in a lab: Imperva’s researchers achieved code execution against a specific Node.js build on Linux, through apps that decompress Brotli responses with
fetch()or accept Brotli-compressed request bodies in Express 5. It took multiple attempts. - Not seen yet: CISA’s assessment lists no known exploitation, the flaw is not on its Known Exploited Vulnerabilities list, and Red Hat says there is no public, reliable code-execution exploit.
- Not established: Claims that specific tools such as curl, Bun or Istio are all exposed haven’t been confirmed in vendor advisories we could find. Any software that relies on a vulnerable copy of the library and decompresses untrusted data could be affected, but each vendor has to confirm its own exposure.
That’s serious enough without the sirens. A widely embedded library has a critical bug, the fix exists, and the window to patch quietly is open right now.
Why a shared library is harder to fix
When a bug lives in one product, one update fixes it. When it lives in a building block, every product that copied that block needs its own fix. Software that uses your operating system’s copy of Brotli is fixed when you update the operating system. Software that ships its own copy, which is common in containers, desktop apps and appliances, stays vulnerable until that vendor ships an update.
That’s the real work here: not panic, but inventory.
What to do this week
- Update Node.js to 22.23.4, 24.22.1 or 26.12.1. If you’re on 20 or earlier, you’re on a version that won’t get this fix, and it’s time to plan the upgrade.
- Update your operating systems’ brotli packages on every server, and rebuild container images so they pick up the fix.
- If you run Envoy with the Brotli decompressor configured, move to a patched release.
- Ask your vendors. Your web developer, hosting provider and any software vendor that processes web traffic for you should be able to tell you whether they’re affected and when they patched.
- Limit what you decompress. Where you can, don’t automatically decode compressed data from sources you don’t trust, and cap the size of compressed uploads at your proxy or firewall.
Where cyber insurance fits
If this flaw is used to get into your systems, a cyber policy is built for what follows: forensic investigation, breach counsel, notification if customer data was exposed, restoring systems and the income you lose while they’re down.
What a policy won’t pay for is the patching itself. Finding affected software and updating it is generally treated as a cost of doing business rather than a covered loss, though your policy wording controls. And timing matters. Some policies reduce coverage for losses that start with a known vulnerability left unpatched past a set number of days, and your application probably asked how quickly you apply critical patches. Fixes have been available since October 21, and that clock is already running.
The headlines will move on. The unpatched copies won’t, until someone updates them.
Sources
- CVE.org: CVE-2026-111497, Out-of-Bounds Write in Google Brotli Decoder
- Node.js: October 2026 security releases
- Imperva: Node2Shell, from Brotli data to remote code execution
- Envoy: Out-of-Bounds Write in Brotli Decompressor (GHSA-3wvj-j6qm-62mr)
- Red Hat: CVE-2026-111497
- Debian Security Tracker: CVE-2026-111497
- PyPI: Brotli