Brotli decoder flaw behind Node2Shell reaches Node.js, Bun and Python
Any program reusing the affected decoder can be crashed or exploited, and projects are patching their own copies until fixed releases ship.

A memory-corruption bug in Google's Brotli decoder, tracked as CVE-2026-111497 and nicknamed Node2Shell, affects versions 1.0.3 through 1.2.0 and reaches any program that reuses that decoder, including Node.js, Bun, Envoy, Istio and Python's Brotli and brotlicffi packages. Crafted compressed input can write past a buffer's end, which may crash a process, leak memory or let an attacker run code. Imperva has run attacker code on an unmodified Node.js 24.22.0 Linux arm64 build, though its exploit is unpublished and succeeded only on some attempts, and no in-the-wild exploitation has been reported. The underlying fix landed in Brotli's source in February but shipped in a release only on October 21, so each downstream project has been patching its own copy, and Microsoft's .NET, Visual Studio and PowerShell updates followed on October 25. Operators should upgrade, restart services and rebuild container images, or refuse Brotli input until they can.
Why it matters
The flaw sits in a shared compression library rather than in any single product, so its reach extends to every project that bundles that decoder. Because each downstream project has been patching its own copy, operators cannot rely on one upstream release to close the gap for them. Until their dependencies are updated, teams that accept Brotli input from outside their networks remain exposed to crashes, memory leaks or code execution.
Matters or hype?
Does this story matter, or is it hype? Vote before you see what everyone else said.