Skip to main content
All incident reports
Incident report

Critical Brotli flaw CVE-2026-111497 prompts emergency patches across .NET and Node.js

A critical out-of-bounds write in Google's Brotli compression library, tracked as CVE-2026-111497, can crash or leak memory and may allow remote code execution when applications decompress attacker-controlled data. Google, Node.js, Microsoft and Python package maintainers have issued fixes, but no in-the-wild exploitation has been reported.

· First published

The short version

  • The flaw. An out-of-bounds write in Google's Brotli decompression library, tracked as CVE-2026-111497, can corrupt memory when a vulnerable decoder processes crafted compressed data. Google scored it 9.2 under CVSS v4; Microsoft rates it 8.1 under CVSS v3.1.
  • The impact. Node.js says the bug can crash a process, leak memory and let an unauthenticated attacker run arbitrary code. Imperva has demonstrated code execution on an official Node.js Linux arm64 build, but no malicious exploitation in the wild has been reported.
  • The patches. Microsoft released emergency updates for .NET, Visual Studio and PowerShell on 25 October. Node.js, Google Brotli and two Python packages also have fixed releases.
  • The caveat. Updating a system-wide Brotli library does not fix applications that bundle their own vulnerable copy, and running services must be restarted after patching.
  • Discovery dispute. Node.js credits members of OpenAI Codex Security with finding the flaw, while BleepingComputer attributes the discovery to Imperva's red team. The sources do not reconcile the two accounts.

Timeline

DateEvent
FebruaryThe root cause was fixed in the Brotli source code, but OpenAI says it was not then known to be a security vulnerability and no newer Brotli release followed.
21 OctoberNode.js and Google released stable fixes for the flaw.
22 OctoberPublic disclosure of the vulnerability.
23 OctoberFixed PyPI packages became available.
25 OctoberMicrosoft published emergency updates for .NET, Visual Studio and PowerShell.

What the flaw does

The bug is an out-of-bounds write in the Brotli decoder, which expands data compressed with Google's lossless algorithm. BleepingComputer describes an invalid block switch being treated as a request for more input, causing the streaming decoder to append bytes to an eight-byte internal buffer until it overwrites nearby memory. Node.js says crafted input can push data past a buffer limit, causing a crash, memory disclosure or arbitrary code execution.

The flaw affects software that passes attacker-controlled data to a vulnerable Brotli decoder, including compressed HTTP request bodies, responses fetched from untrusted servers and compressed files. Microsoft says .NET and ASP.NET Core do not enable Brotli decompression by default; applications are exposed only if they opt in to request decompression, automatic response decompression or the Brotli APIs.

The vulnerability is known as Node2Shell, HTTP2Shell and Broccoli2Shell because it was first identified in Node.js and later found across other ecosystems. SecurityWeek describes the affected Brotli range as 1.0.3 through 1.2.0, while BleepingComputer lists 1.0.3 to 1.0.9, 1.1.0 and 1.2.0.

Patches and exposed software

Microsoft's 25 October updates cover .NET 8, 9, 10 and 11 Release Candidate 3, Visual Studio 2019, 2022 and 2026, and PowerShell 7.4, 7.5 and 7.6. Microsoft rates the flaw critical for .NET and Visual Studio and important for PowerShell, with an exploitability assessment of more likely exploitation. It also says unpatched .NET installations in non-default configurations may allow remote privilege escalation.

Node.js and Google released stable fixes on 21 October, and PyPI packages carrying fixes became available on 23 October. SecurityWeek reports that Bun, Envoy and Istio have also been updated. For the upstream library, Brotli 1.2.1 is a fixed release; administrators should consult each vendor for the full list of patched versions.

A tracker of software that bundles its own Brotli decoder listed DuckDB, Apache Arrow, 7-Zip-zstd, p7zip and EDK II as unpatched, though its maintainers say the list is incomplete and not every configuration exposes the vulnerable code. Updating the system library does not fix these bundled copies. Patching also requires restarting running processes and rebuilding container images on a patched base.

Discovery and exploitation status

The sources disagree on who found the flaw. SecurityWeek says Node.js credited members of OpenAI Codex Security, and OpenAI says the issue was uncovered during red-teaming before it notified Brotli's developers and dependent projects. BleepingComputer says Imperva's red team found it. No source explains the discrepancy.

Imperva has shown code execution on the official Node.js 24.22.0 Linux arm64 image, sending malicious data in both a server response and a request body. The firm says the proof did not succeed on every attempt and has not made its exploit public. A GitHub proof-of-concept reportedly works only against an intentionally weakened build, and some researchers argue the bug can only cause denial of service.

No exploitation in the wild has been reported. The sources note published proof-of-concept exploits, but none reports malicious use. OpenAI says the root cause was fixed in Brotli's source code in February before the security impact was understood.

What is not known yet

  • Who first discovered the flaw, given the conflicting credits to OpenAI Codex Security and Imperva's red team.
  • Whether anyone has attempted malicious exploitation beyond the published proofs of concept.
  • How many applications or organisations remain exposed through bundled Brotli copies, since the public tracker is incomplete.
  • Whether Imperva's code-execution proof extends beyond the specific Node.js Linux arm64 configuration it tested.
  • Which vulnerable version range is authoritative, because the sources describe it differently.

What to do

If you use affected Microsoft, Node.js or Python software

  1. Apply the vendor updates for .NET, Visual Studio, PowerShell, Node.js, and the Python Brotli and brotlicffi packages; consult each advisory for fixed versions.
  2. Check whether your application has opted in to Brotli decompression through ASP.NET Core request decompression, HttpClient automatic response decompression or the System.IO.Compression Brotli APIs.
  3. Restart affected services after patching.

If you run applications that bundle their own Brotli decoder

  1. Inventory those bundled copies and update them directly; updating only the system Brotli library does not remove the risk.
  2. If patching is delayed, block inbound Brotli-compressed requests at the proxy or firewall and remove Brotli support from Python applications where possible.
  3. Do not rely on inbound blocking alone, because it does not cover malicious compressed responses fetched from untrusted servers.
  4. Rebuild and redeploy container images on a patched base.

For everyone else

  1. Treat decompression libraries as part of the attack surface and monitor vendor advisories for products that embed Brotli.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.