HTTP2Shell vulnerability in Brotli demands emergency updates

A critical flaw known as the HTTP2Shell vulnerability (CVE-2026-111497) was reported in the Brotli C decoder, and it can let attackers corrupt memory and access sensitive data, according to BleepingComputer. The bug was first seen in Node.js, and researchers later found the same decoding flaw in Brotli itself, which means multiple ecosystems are affected.

What the HTTP2Shell vulnerability is and why it matters

According to BleepingComputer, the flaw is a buffer overflow in the Brotli streaming decoder. A specially crafted Brotli-compressed stream can trigger an invalid block switch that the decoder treats as needing more input, which causes it to keep appending bytes to an eight-byte internal buffer and write past its bounds. That memory corruption can crash processes, expose memory contents, and, in some cases, enable remote code execution, per Node.js advisories and a confirmation from security company Imperva.

BleepingComputer notes the vulnerability is tracked as CVE-2026-111497 and has been reported under several names, including Broccoli2Shell and Node2Shell. Although the nickname HTTP2Shell highlights the impact on HTTP clients and servers, the issue is not specific to HTTP/2 and applies to any application that decompresses attacker-controlled Brotli data.

Potentially affected software includes Node.js, Python HTTP clients configured to use a vulnerable Brotli decoder (for example urllib3[brotli], requests, httpx, and aiohttp[speedups]), and other applications that bundle the vulnerable Brotli implementation. Microsoft also issued an emergency update for .NET to address the issue, according to BleepingComputer.

Which versions were affected and where fixes are available

BleepingComputer reports that the vulnerable Brotli versions include 1.0.3 through 1.0.9, plus 1.1.0 and 1.2.0. Upstream fixes were first committed to the Brotli project earlier in the year, and stable fixes were released by Node.js and Google on October 21, with PyPI packages containing the fixes published on October 23.

Patched releases listed by BleepingComputer include Google Brotli 1.0.10, 1.1.1, and 1.2.1; Node.js 22.23.4, 24.22.1, and 26.12.1; Python Brotli 1.2.1; and Python brotlicffi 1.2.1.0. Administrators should consult their software vendors and package managers for those updates and apply them where appropriate.

Practical steps for small teams and nonprofits

Apply the available updates as a priority. The public disclosure and the appearance of proof-of-concept exploits make this an urgent patching task, even though BleepingComputer says there are no confirmed reports of exploitation in the wild yet. Practical steps you can take now include:

• Inventory: Identify services and applications that use Brotli or bundle a Brotli decoder, including Node.js services, Python HTTP clients configured with Brotli, and any custom tools.
• Patch: Update to the patched Brotli and runtime versions listed above as soon as you can using your normal change process.
• Restart and redeploy: After updating, restart affected processes and rebuild and redeploy any container images that include a bundled Brotli library, as BleepingComputer advises.
• Temporary mitigations: If you cannot update immediately, remove Brotli support from Python applications and block incoming Brotli-compressed requests at your proxy or firewall, per the guidance in the report.
• Note limitations of some mitigations: Updating the system Brotli library does not fix cases where applications bundle their own copy, and blocking inbound Brotli requests does not stop exploitation via malicious HTTP responses to clients, according to the advisory tracked by BleepingComputer.

How this may affect your deployments

Small web services and API clients that fetch compressed responses are a realistic path for exploitation. An attacker could serve a malicious Brotli-compressed HTTP response to a client, or send a specially compressed request directly to a server that decompresses Brotli data. Any application that handles attacker-controlled compressed input is potentially at risk if it uses a vulnerable decoder.

Because some runtimes and packages bundle their own copy of the Brotli decoder, a system-level update may not be enough. BleepingComputer says the upstream fixes were available earlier in the year, but stable patched packages and runtime releases arrived in late October, so you need to update each affected component in your stack.

What to watch next and where to get help

Proof-of-concept exploits for the Node2Shell variant have been published, raising the urgency of applying patches. Monitor your software vendors and package feeds for updates, and follow proven deployment practices: patch in a controlled window, test, then roll updates to production. If you want to check your external exposure quickly, start with a free external scan.

If you run managed services or use third-party libraries, open a support ticket with those providers to confirm they have applied patched Brotli builds. Keep an eye on further advisories from your platform vendors and on the dedicated portals tracking this vulnerability for any new mitigation guidance.

This is a cross-ecosystem vulnerability that touches core compression code, so prioritize it like other critical memory corruption issues: inventory, patch, restart, and mitigate where immediate updates are not possible.