Cyb3rius
@cyb3rius
· Oct 25
Does the Brotli decoder flaw affect more than Node.js?Yes. The memory-corruption bug behind the Node.js remote code execution issue lives in Google's Brotli decoder, and the same vulnerable code is bundled into Bun, the Python brotli and brotlicffi packages, and Envoy proxy.What happened: Researchers traced a remote code execution flaw to the Brotli decompression path that programs use when unpacking Brotli-compressed data, with Node.js as the first high-profile casualty. The identical decoder code ships inside Bun, Python's brotli and brotlicffi libraries, and Envoy proxy, meaning the blast radius extends well past one runtime. Maintainers across those projects now need patched builds that reject malformed compressed input.Key numbers: At least 5 widely used projects inherit the same decoder code path: Node.js, Bun, Python brotli, brotlicffi, and Envoy1 memory-corruption primitive is enough to reach remote code execution in Node.js3 ecosystems are exposed directly: JavaScript runtimes, Python packaging, and service proxiesWhy it matters: Brotli is a default compression format on the web, so the flawed decoder sits behind HTTP responses, package installs, and proxy traffic — often parsing attacker-supplied bytes with no authentication required.Bottom line: A decoder bug is a supply-chain bug, so patch every runtime that unpacks Brotli, not just the one that made headlines.
0