A critical flaw nicknamed "Node2Shell" — also called "Broccoli2Shell" or "HTTP2Shell" — sits in the Brotli compression library used by Node.js and a long list of other widely used software, and CISA confirmed in late October that hackers have begun exploiting it, adding it to its Known Exploited Vulnerabilities catalog and ordering federal agencies to patch (BleepingComputer, 2026; Help Net Security, 2026). The federal patch deadline has already passed, but if your business runs web servers, APIs, or containerized applications, the exposure doesn't end there — this is worth checking regardless of whether you're a federal agency.
What Is the Actual Vulnerability?
CVE-2026-111497 is an out-of-bounds write flaw in the Brotli decoder — the code that decompresses data compressed with Google's Brotli algorithm, commonly used to shrink web traffic. When an application decompresses a specially crafted Brotli stream, the bug can corrupt adjacent memory in the decoder, which Node.js's own advisory says "can lead to a crash, disclosure of process memory, or remote code execution." Unlike many vulnerabilities that require a logged-in user or specific configuration, this one can be triggered by an unauthenticated attacker simply sending malicious compressed data to anything that decompresses it.
Why Does This "Reach Far Beyond Node.js"?
Because the flaw isn't in Node.js itself — it's in the underlying Brotli library that Node.js happens to bundle, and plenty of other software bundles the same library. Security firm Tenable put it plainly: "any application that decompresses attacker-controlled data with a vulnerable Brotli decoder is potentially at risk, including Node.js, .NET, Bun, Envoy Proxy, Istio, Python HTTP clients, FFmpeg, Apache Arrow and ClickHouse." Several Linux distributions have also released or are releasing their own patched packages. If your business runs any modern web stack, there's a reasonable chance one of these components is somewhere in it.
How Long Was This Sitting Out There?
Longer than it should have been. The actual fix was quietly committed to Google's open-source Brotli code repository on February 27, 2026 — with no public release and no security advisory attached to it. That fix sat publicly visible in the code for roughly eight months before Node.js disclosed the vulnerability on October 21, 2026, at which point the Brotli project rushed out patched library versions (1.2.1, 1.1.1, and 1.0.10) the following week. That gap matters because it means the fix was technically available to anyone who went looking, including attackers, well before most affected organizations knew there was anything to patch.
Is This Actually Being Exploited Right Now?
Yes. Security researchers at Imperva demonstrated working remote code execution against an official Node.js Docker image, and threat-intel firm ELLIO reported observing real exploit traffic in the wild, tied to a source IP that has also been used for PHP2Shell exploitation and scanning against Palo Alto GlobalProtect, FortiOS SSL VPN, and Kubernetes API endpoints. ELLIO's read: that pattern "is indicative of the RCE being adopted by an operator focused on mass exploitation" — not a single targeted attack, but broad opportunistic abuse. Proof-of-concept exploit code has also been published on GitHub, which tends to accelerate copycat attacks. CISA added the flaw to its KEV catalog around October 27-28 and issued Binding Operational Directive 26-04, giving federal agencies until November 10 to patch — a deadline that has already come and gone.
Which Versions Are Fixed?
For Node.js specifically, the affected release lines are 26.x, 24.x, and 22.x, fixed in versions 26.12.1, 24.22.1, and 22.23.4. If you're running an end-of-life Node.js line — 20.x, 23.x, or 25.x — those versions are confirmed affected but will not receive a fix at all, meaning an upgrade to a supported release line is the only path forward. For every other affected product (.NET, Bun, Envoy, Istio, FFmpeg, and the rest), check that specific vendor's advisory, since fixed versions and exposure vary by product.
What Should a Business Do About This?
Patch any Node.js, .NET, or other affected runtime to a fixed version, and don't stop there: restart the affected processes, and if you run containers, rebuild and redeploy any container images built on an older, vulnerable base — an unpatched image baked weeks ago stays vulnerable even after the underlying host is updated. Where immediate patching isn't possible, security teams are advising two stopgaps: block incoming Brotli-compressed requests at the proxy or firewall level, or disable Brotli decompression entirely until you can update. Given how broadly this library turns up — well outside of Node.js — it's also worth asking your development or hosting provider directly whether any of your externally-facing applications process Brotli-compressed data through an affected component.
