Trusence Every claim has a source
Last updated 25 October 2026 Search Türkçe
Security

Brotli decoder flaw CVE-2026-111497 reaches Node.js, Bun and Python packages

Each affected project ships its own copy of the decoder, so every runtime and library needs its own update before the fix takes effect.

A cracked brick resting in front of a key left in a lock, both on a wooden table beside a small stack of sealed crates.
AI-generated illustration

A memory-corruption bug in Google's Brotli decompression code, tracked as CVE-2026-111497, can let crafted compressed input overwrite memory past a buffer's end, with outcomes ranging from crashes to attacker-controlled code execution. Because each downstream program bundles its own copy of the decoder, Bun, Node.js, Envoy, Istio and several Python packages each need their own update. Imperva showed code execution on one unpatched Node.js 24.22.0 build, though that exploit has not been published and was not tested on other builds. No in-the-wild attacks have been reported, and Google rates the flaw 9.2 critical while Red Hat scores it 8.1. The underlying fix reached Brotli's source in February but no release carried it until October 21, so the practical remedy is updating the affected runtime or library and restarting services.

Why it matters

The flaw lets crafted compressed input write past a buffer's end, and its severity is rated differently by Google and Red Hat. Because the fix sat in Brotli's source code from February 27 without a release until October 21, software built on the decoder stayed exposed for months after the patch existed. Projects that bundle Brotli must now ship their own updates, and a running process keeps the old decoder until its service is restarted.

Sources · 1

Checked against its sources before publishing · 25 October at 11:17