🔍 Read the full analysis: Broccoli2Shell: A Compression Issue With Reach Beyond One Language on ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
A memory-corruption flaw in Google’s Brotli decoder, tracked as CVE-2026-111497, affects versions 1.0.3 through 1.2.0 and has prompted fixes across runtimes and packages. A security firm demonstrated code execution in an unmodified Node.js build, but CISA data lists no known exploitation in the wild. Developers need to apply the relevant patched release and restart running processes.
A critical flaw in Google’s Brotli decoder affects versions 1.0.3 through 1.2.0, prompting security updates across Node.js, Python packages and other software that uses the compression library. The vulnerability, tracked as CVE-2026-111497 and nicknamed Broccoli2Shell, can corrupt memory when a decoder handles malformed compressed data; Imperva reported running code in a demonstration against an unmodified Node.js build.
The flaw is in the shared Brotli C decoder, rather than in every affected application separately. According to the Node.js advisory, a particular malformed stream could be treated as incomplete input instead of invalid data. The decoder could then write beyond an eight-byte internal buffer. Memory corruption can cause a crash or expose data, and may allow code execution, though the demonstrated result is not evidence that every affected deployment can be exploited in the same way.
Fixes listed in the source material include Brotli 1.0.10, 1.1.1 and 1.2.1; Node.js 22.23.4, 24.22.1 and 26.12.1; Python Brotli 1.2.1 and brotlicffi 1.2.1.0; Bun 1.4.4; and updated releases of Envoy, Istio and .NET. These version numbers are reported as current on October 26, 2026. Node.js 20, 23 and 25 are listed as receiving no fix.
Updating software is not enough if a vulnerable process keeps running. The report says the old decoder remains loaded until the process restarts, so operators must patch and restart affected services. Exposure depends on how software uses Brotli: examples include automatically decoding fetched responses, accepting compressed request bodies, or processing files. A bare Node.js HTTP server does not decode request bodies by itself, according to the source.
Infographic 01 · Where Brotli decoding meets untrusted input
One decoder, many doors.
The flaw sits in Google's Brotli C decoder. Every runtime, package and tool that copies it inherits the bug. Three paths bring attacker data to it.
Responses your code fetches
no WAF sees these
- Node.js
fetch()decodes Brotli automatically - Python
requests,urllib3,aiohttp,httpx[brotli], Scrapy, once a Brotli package is installed - Webhooks, link previews, crawlers, “import from URL”
Request bodies you accept
WAF can block br bodies
- Express 5.0.0–5.3.0 and body-parser 2.0.0–2.3.0 inflate Brotli bodies (
json(),raw()) - Upgrading Express alone does not help: the bug is in the runtime
- A bare Node.js HTTP server does not decode bodies on its own
Files you open or process
not only HTTP
- Archives and
.brfiles (7-Zip-zstd, p7zip) - Parquet data files (DuckDB, Apache Arrow bundled build)
- Fonts (woff2), firmware tools (EDK II), JPEG XL via libjxl
Fixed versions
patch, then restart a running process keeps the old decoder
| Component | Fixed in | Note |
|---|---|---|
| Google Brotli (C library) | 1.0.10 · 1.1.1 · 1.2.1 | 1.0.3–1.2.0 |
| Node.js | 22.23.4 · 24.22.1 · 26.12.1 | 20, 23, 25: no fix (end of life) |
Python Brotli / brotlicffi | 1.2.1 / 1.2.1.0 | 1.0.3 up to 1.2.0.x |
| Bun | 1.4.4 | includes Brotli 1.2.1 |
| Envoy Proxy | 1.40.0 · 1.39.3 · 1.38.6 · 1.37.8 | if Brotli decompression is configured |
| Istio | 1.29.9 · 1.30.6 · 1.31.2 | 1.29 is end of life |
| .NET runtime | 8.0.33 · 9.0.22 · 10.0.14 | GitHub source builds still affected |
Debian brotli | bookworm 1.0.9-2+deb12u1 · trixie 1.1.0-2+deb13u1 | DLA 4855-1 · DSA-6582-1 |
Official Node.js builds bundle their own Brotli, so only the Node.js version matters there; some distributions (Debian, Ubuntu 22.04+) build Node.js against the system library instead.
Sources: CVE record (Google CNA, CISA ADP 23 Oct); Node.js (21 Oct 2026); GHSA-9v8h-qqgm-4m35; Brotli releases (21 Oct 2026); Patch the Planet (23 Oct 2026); Imperva (22 Oct 2026); broccoli2shell.com (26 Oct 2026); OpenSourceMalware (23 Oct 2026); Debian tracker; pypistats.org (26 Oct 2026).
Powered by Thorsten Meyer AI
One Decoder, Many Software Stacks
The vulnerability matters because Brotli is reused across products and programming languages. A flaw in one decoder can therefore require coordinated fixes in libraries, runtimes, packages, distributions and container images. Developers cannot assume that updating a high-level framework will fix the underlying decoder: the source says the issue is not in Express itself, and upgrading Express alone does not address it.
Patch status also varies by how software is built. Official Node.js builds bundle Brotli, making the Node.js release version relevant; some Linux distributions instead link against a system library. The source’s tracker listed seven bundled copies still unfixed as of October 26, including copies associated with DuckDB, Apache Arrow, 7-Zip-zstd, p7zip and EDK II firmware tools. That tracker is a developing inventory, not confirmation that every use of each product is exposed.
The immediate practical consequence is a supply-chain check: teams need to identify whether a vulnerable decoder is present, determine whether untrusted compressed input can reach it, and confirm that updates are active in running services. The source also reports that Python’s Brotli package had about 83 million downloads in the prior month, citing pypistats.org as checked October 26. That is a download count, not a measure of vulnerable installations or exploitation.
Products Worth Considering

Samsung 32 Odyssey G5 QHD Gaming Monitor

LG UltraGear 27-inch QHD OLED Gaming Monitor, 240Hz, 0.03ms, G-SYNC Compatible, FreeSync Premium Pro, HDR True Black 400

LG 27GS60QC-B Ultragear 27-inch Curved Gaming Monitor (QHD, 180Hz, 1ms, 1000R)
As an affiliate, we earn on qualifying purchases.
From February Fix to October Disclosure
The timeline helps explain why updates now span many projects. The source reports that the root-cause change entered Brotli’s source code on February 27, 2026, in a commit titled “Detect and report invalid stream earlier.” It says the change did not identify itself as a security fix. Releases carrying the correction appeared on October 21, a 236-day gap. OpenAI said the security significance was not known at the time and that Brotli had not had a more recent release.
Node.js issued a security release on October 21, initially listing the Brotli issue among several vulnerabilities. The CVE became public on October 22, alongside a public proof of concept, according to the source’s tracker. Updates have since appeared for Python packages and other software. The source says a tracker identified more than 30 projects and packages bundling their own copy, while some projects were still awaiting releases as of October 26.
The CVE record, filed by Google, describes an out-of-bounds write and an unchecked return value. The record assigns a CVSS 4.0 score of 9.2, rated Critical. That severity rating describes the assessed risk; it does not establish that attacks are occurring in real-world deployments.
Exposure and Exploitation Remain Open
The available information does not establish how many systems are vulnerable or whether attackers have exploited the flaw outside demonstrations. The source says CISA data lists exploitation as “none” and that CVE-2026-111497 was not in CISA’s Known Exploited Vulnerabilities catalog as of October 26. Those indicators do not prove that exploitation is impossible or that every system has been checked.
Imperva reported achieving code execution on an official Node.js image after several attempts. That is a reported demonstration, not evidence of a successful attack campaign. The practical risk for any given service depends on its decoder version, build configuration, exposure to attacker-controlled compressed data and runtime protections. The source also notes that some affected bundled copies had not yet received fixes, but their exact exposure and release timelines remain unresolved.
The reported download figure for Python’s Brotli package cannot show how many vulnerable copies remain active. Nor does a package’s presence alone establish that untrusted input reaches its decoder. Those deployment-level details are not supplied in the source material.
Patch Releases and Restart Checks
Administrators should check the versions used by applications, operating-system packages and bundled dependencies against the relevant vendor advisories, then install a fixed release where available. They should also restart affected processes so the updated decoder is loaded and verify that production instances, not just build files, are running the patched versions.
Teams using software whose bundled copy remains unpatched will need to follow that project’s security notices and assess whether processing untrusted compressed data can be limited until an update is available. The source reports that five additional projects had fixes in their main development branches, but a fix in a development branch is not necessarily present in a released product.
The immediate next developments are likely to be further package and distribution advisories, updated bundled copies and clearer inventories of affected versions. The source material does not provide a common deadline for those releases. Security status should be checked against current vendor notices, since the package list and patch availability may change after October 26.
Key Questions
What is Broccoli2Shell?
Broccoli2Shell is the nickname for CVE-2026-111497, a flaw in Google’s Brotli decoder. Malformed compressed input can cause an out-of-bounds memory write, according to the CVE and advisories cited in the source.
Which software is affected?
The source identifies vulnerable Brotli versions 1.0.3 through 1.2.0 and lists affected or potentially affected software that uses or bundles the decoder, including Node.js, Python Brotli packages, Bun, Envoy, Istio and .NET. The precise affected version depends on the product and how it was built.
Is the flaw being exploited in the wild?
The source says CISA data listed exploitation as “none” and the CVE was not in CISA’s Known Exploited Vulnerabilities catalog as of October 26, 2026. Imperva reported a code-execution demonstration, but the source does not establish real-world exploitation.
What should operators do after installing an update?
Install the fixed release that matches the product and deployment, then restart affected processes. The source says a running process can continue using the old decoder until it restarts; operators should verify the version actually loaded in production.
Source: ThorstenMeyerAI.com
