🔍 Read the full analysis: Broccoli2Shell: Prepare A Patch, Restart Services, And Validate The Result on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
A flaw in Google’s Brotli decoder, tracked as CVE-2026-111497, affects multiple runtimes and applications that bundle or use vulnerable versions. Fixes are available for several projects, but operators must also restart running services; some bundled copies remained unfixed as of October 26, 2026. No exploitation in the wild was reported in the cited sources.
CVE-2026-111497, a memory-corruption flaw in Google’s Brotli decoder, is prompting security updates across software that uses the compression library, including Node.js and Python packages. ThorstenMeyerAI.com reported on October 26 that fixes are available for several major projects, but operators need to update affected components and restart running services to load the patched decoder.
The vulnerability affects Brotli C decoder versions 1.0.3 through 1.2.0, according to the source report. The Node.js advisory describes malformed compressed input that the decoder can treat as incomplete rather than invalid. That handling can cause a write past an internal buffer, potentially crashing a process, exposing memory or, in a severe case, enabling code execution. The CVE record lists an out-of-bounds write and an unchecked return value.
Fixes listed in the report 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; and Bun 1.4.4. Updates are also listed for Envoy, Istio, .NET and Debian releases. Node.js versions 20, 23 and 25 are identified as receiving no fix, so users of those branches should consult the relevant project guidance on supported versions and migration.
Exposure depends on how software uses Brotli. The report says Node’s built-in fetch decodes compressed responses, while Python clients may do so when a Brotli package is installed. Some Express and body-parser versions can inflate Brotli request bodies, but the report stresses that the flaw is in the decoder, not Express itself. A library or runtime update may not fix a separately bundled copy.
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
Why Restarting Matters
The issue illustrates how a flaw in a shared parsing library can reach applications through multiple layers of a software stack. A team may not have installed Brotli directly: a runtime, framework, proxy, distribution package or bundled dependency may include it. That makes an inventory of actual deployed components more useful than checking only an application’s top-level dependencies.
Updating files is not the same as updating live processes. According to the source report, an already-running service continues using the decoder loaded in memory until it is restarted. Administrators should identify where Brotli decoding occurs, apply the correct vendor or distribution update, restart affected processes, and verify the running version. The cited report does not establish that every installation is exposed; exposure depends on the versions and features in use.
The timing also matters for software supply chains. The report says a source-code change correcting the behavior was committed on February 27, 2026, while releases containing the fix appeared on October 21. It describes that as a 236-day interval before release, followed by the need for downstream projects to prepare and distribute their own updates.
Products Worth Considering

Dell XPS Tower 8960 Desktop, Intel Core i7-13700, NVIDIA GeForce RTX 4060, 16GB DDR5, 512GB SSD

Samsung 27-Inch M5 (M50F) FHD Smart Monitor

Canon SELPHY CP1500 Wireless Photo Printer Bundle with 108 Sheets of Photo Paper
As an affiliate, we earn on qualifying purchases.
How the Fix Spread Across Projects
The flaw became public in October. The source report says the CVE was disclosed on October 22 and a public proof of concept appeared that day. It also reports that releases carrying the fix began on October 21. The distinction between a fix in a library’s source and a patch available to users is central: projects that bundle their own copy must incorporate and ship the correction separately.
Node.js credits OpenAI Codex Security in its advisory. OpenAI said it found the flaw during red-teaming with teams of AI agents. The report also attributes a statement to OpenAI that the February change was not then known to create a security vulnerability and that no newer Brotli release was available at the time. These are attributed accounts of discovery and release timing, not evidence that all downstream maintainers had the same information.
As of October 26, the article says an independent tracker listed more than 30 projects and packages with bundled copies, including seven still without a fix. It names DuckDB, Apache Arrow’s bundled build, 7-Zip-zstd, p7zip and EDK II firmware tools among those still affected. The status can change as maintainers publish updates, so users should check the current advisory for each component.
Which Bundled Copies Remain Exposed
The status of every downstream package is not settled. The report’s tracker listed seven bundled copies without fixes as of October 26, while five additional projects had fixes in their main development branches but not necessarily in releases. Those counts may change, and the article does not establish whether every named project is deployed in a vulnerable configuration.
The cited sources report no known exploitation in the wild: Google’s CVE record gives the issue a 9.2 Critical score under CVSS 4.0, while the report says CISA data lists exploitation as “none” and the CVE was not in CISA’s Known Exploited Vulnerabilities catalog. Imperva reportedly demonstrated code execution on an official Node.js image after several attempts. That demonstration indicates a possible impact under test conditions; it is not evidence of real-world exploitation.
It is also unclear from the source material how many systems are exposed, whether a given deployment accepts attacker-controlled Brotli data, and when each remaining project will publish a patched release. The report’s separate mention of DreamHost resetting some email and FTP/SFTP passwords is not linked to Brotli; it says DreamHost named no cause.
Patch, Restart and Verify
Operators should first identify affected runtimes, packages, operating-system builds and bundled libraries, then consult their vendors’ current security advisories. Apply a fixed release appropriate to the deployed component. Where no update is listed, track the maintainer’s advisory and consider the project’s own mitigation guidance rather than assuming that updating an unrelated framework resolves the decoder flaw.
After applying updates, restart services and workers that may have loaded the vulnerable decoder. Verify the versions actually running, including in containers and systems where the operating system supplies a shared library. Teams should also review services that decompress remote responses, incoming request bodies or files, while avoiding assumptions that a component is vulnerable solely because it can support Brotli.
The next development is the release of fixes for remaining bundled copies and confirmation that downstream packages and deployed images include them. The source report gives no final completion date. Security teams should use current project advisories and distribution notices, since the October 26 tracker snapshot may no longer reflect the latest patch status.
Key Questions
What is Broccoli2Shell?
It is the name used in the source report for the CVE-2026-111497 Brotli decoder flaw. The issue involves malformed compressed input that can trigger memory corruption in affected decoder versions.
Which Node.js versions have fixes?
The report lists Node.js 22.23.4, 24.22.1 and 26.12.1 as fixed releases. It says Node.js 20, 23 and 25 do not receive a fix; users should check current Node.js guidance for supported upgrade paths.
Is updating a package enough?
Not for a process that is already running. The report says a running service retains the decoder it loaded until it restarts. Apply the appropriate update, then restart and verify the version used by the live process.
Has the flaw been exploited in the wild?
The source report says the cited CISA data lists exploitation as “none” and that the CVE was not in CISA’s Known Exploited Vulnerabilities catalog as of October 26, 2026. Imperva’s reported code-execution demonstration was a test, not evidence of real-world exploitation.
Are all affected projects patched?
No. The report said an independent tracker still listed seven bundled copies without fixes on October 26, 2026. Check current advisories for each runtime, package, distribution or application because patch status can change.
Source: ThorstenMeyerAI.com
