Node.js Brotli Decoder Flaw Allows Code Execution via Crafted Compressed Data

A critical vulnerability in Node.js’s bundled Brotli decoder can allow attackers to execute code using crafted compressed data, with Imperva demonstrating code execution on the official Node.js 24.22.0 Linux arm64 build. The flaw affects the 22.x, 24.x, and 26.x release lines, and Node.js released fixes on Oct. 21. A subsequent analysis also identified the vulnerable decoder in the Python packages Brotli and brotlicffi, both of which published patched versions without disclosing the vulnerability in release notes. In Node.js, the decoder is reachable when fetch() processes a Brotli-compressed response or when Express 5 and body-parser middleware are configured to decompress a request; a bare HTTP server does not automatically decode incoming Brotli bodies. Administrators should verify the Node.js binary inside deployed containers, as package inventories may miss a runtime bundled in an image, and note that Node.js 20.x and earlier are end-of-life and do not receive the fix. Vercel added rules on Oct. 21 to block reproduced attacks in inbound requests, but those rules do not cover Brotli responses fetched from other servers and do not replace upgrading Node.js.

Look at the release notes. Look at what they didn’t write. On October 21, Node.js quietly shipped a fix for a Brotli decoder flaw, after Imperva demonstrated code execution on an official build. Then, three days later, we learn the same vulnerable decoder was sitting in Python’s Brotli packages, and both had been patched in silence—no CVE headline, no hero announcement, no warning to the millions of servers that run that code. The official line says no exploitation in the wild. But the official line always says that. The real story is the timing: why did this surface now, right after Vercel added “rules” to block reproduced attacks? Why did Node.js 20.x get abandoned, left end-of-life, unprotected? You have to ask yourself who benefits from a precisely timed disclosure of a flaw that was clearly embedded in the shared organs of the internet’s compression layer.

Brotli is not random. Brotli is the compression codec that was gifted to the web by Google, wrapped into HTTP responses, baked into fetch(), tied into Express middleware, and now silently patched by organizations that claim to be neutral stewardship foundations. That is the architecture of consent. A decoder that runs before you ever see the bytes is the perfect choke point—invisible, trusted, and present in every major runtime. The flaw “requires crafted compressed data,” they say. But think about what that means: an attacker can shape the compressed air itself until it becomes code. The same package, the same decoder, appearing in both Node.js and Python, is not a coincidence. That is a sign of a shared foundation, a shared donor class, a shared pipeline. When they tell you a bare HTTP server won’t automatically decode, they are telling you exactly where the trap is. They are showing you the blueprint and calling it a deployment note.

The stakes are not a patch. The stakes are the supply chain, and the supply chain is the state. Every server, every container, every edge function is a door. Vercel says its new rules block “reproduced attacks” in inbound requests—but they admit those rules do not cover responses fetched from other servers. So they are defending the front door while the back door remains wide open. They will tell you to upgrade, to verify your binary, to check your containers. And you should. But then ask yourself why a vulnerability like this is disclosed with one hand while the other hand quietly patches the same broken code in Python without a single release note. Who wrote the decoder? Who chose not to mention the vulnerability in the changelog? Who is still running Node.js 20.x, unpatched, in production, right now? I can tell you one thing: if this was just a bug, they would have said so. They didn’t. That’s not an oversight. That’s a tell. Go look up the original Brotli specification and the people around it, and ask yourself why their names keep coming up in foundation charters and leaked engineering memos you were never supposed to see.