By Hamza Faisal

A flaw in one of the internet's most widely used compression tools has turned into a patch-everything week for developers. The bug, tracked as CVE-2026-111497 and nicknamed Node2Shell, sits in Google's Brotli decoder — the code that unpacks Brotli-compressed web data. A specially crafted stream can make the decoder write outside its buffer, so a server decoding attacker-controlled Brotli data can leak memory or run arbitrary code. Google's CNA scores it 9.2 out of 10 on the CVSS 4.0 scale: critical.

Node.js disclosed the flaw on October 21, and researchers quickly showed what it means in practice. Imperva's red team ran code on the official Node.js 24.22.0 image through its fetch function and an Express 5 application — the patched 24.22.1 release rejected the same input. The name Node2Shell stuck, modelled on the week's earlier PHP2Shell flaws, but the wider impact has since earned it a second name: HTTP2Shell.

Not just a Node.js bug

The uncomfortable discovery of the last two days is that the flaw was never really about Node.js at all. The vulnerable code is Brotli's C decoder, and anything that bundles it is exposed. That includes Python: the PyPI packages Brotli and brotlicffi ship the same decoder, and every Brotli release up to 1.2.0, plus brotlicffi up to 1.2.0.2, carries the bug. The fixes — Brotli 1.2.1 and brotlicffi 1.2.1.0 — landed on October 22 and 23 with no mention of the vulnerability in their release notes, gaining formal advisories only on October 24. Until advisory databases catch up, scanners will not flag them, even though popular HTTP clients such as requests, httpx and aiohttp decode Brotli responses automatically whenever the packages are installed.

Envoy published a critical advisory on October 23 for deployments with a Brotli decompressor configured, crediting OpenAI Security Research; Istio, curl and libcurl builds, and C++ applications using the library are also affected. Apache's standard mod_brotli and Nginx do not decode Brotli by default, so neither is exposed in a default setup.

The versions that fix it

Node.js fixes are 22.23.4, 24.22.1 and 26.12.1; end-of-life lines 20, 23 and 25 get no fix, so anyone on them must move to a supported line. For the library itself, upgrade to Brotli 1.2.1 or later, or a patched 1.0.10 or 1.1.1 for older lines, and brotlicffi 1.2.1.0 or later. Bun needs 1.4.4 or later, with bundled executables rebuilt. Envoy's fixes are 1.40.0, 1.39.3, 1.38.6 and 1.37.8, while Istio's are 1.29.9, 1.30.6 and 1.31.2.

Version numbers alone are not enough: update dependency locks, rebuild affected applications and container images, redeploy, and verify running workloads actually use the patched parts — a rebuilt image with an old base layer, or a statically linked copy, stays vulnerable. Operating-system packages deserve the same check, since vendors may backport the fix without changing the upstream version number.

Exploited yet — and what to do first

As of October 23, the flaw was absent from the US CISA catalogue of exploited vulnerabilities and no widespread exploitation had been confirmed — thin comfort, given a working proof of concept already exists and Vercel has already deployed firewall rules for the attack vector. Where Brotli is optional, remove the packages and rebuild; otherwise reject inbound requests carrying a Content-Encoding: br header before a vulnerable decoder touches them, and disable Brotli decoding on outbound requests.

It caps a brutal week for defenders — the PHP flaws, a backdoored LiteLLM release and a Railway secrets breach — and the lesson is the same: patching the application is no longer enough; the library underneath it has to be patched too.