🔍 Read the full analysis: Broccoli2Shell For Operators: Patch Dependencies And Check Running Services on ThorstenMeyerAI.com
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
A flaw in Google’s Brotli decoder, tracked as CVE-2026-111497, affects versions 1.0.3 through 1.2.0 and has reached multiple runtimes and software packages. Fixes are available for several platforms; operators need to update affected components and restart running processes. A code-execution demonstration has been reported, but CISA data says there is no known exploitation in the wild.
Operators using Brotli should update affected runtimes and packages and restart services after patching, following disclosure of CVE-2026-111497, a flaw in Google’s Brotli decoder. The issue affects decoder versions 1.0.3 through 1.2.0 and can cause memory corruption; Imperva reported running code in a demonstration against an unmodified Node.js build. CISA data cited in the source says exploitation is not known in the wild.
The vulnerability arises when the decoder treats malformed compressed input as incomplete data, according to the Node.js advisory described by ThorstenMeyerAI.com. The decoder can then write beyond an eight-byte internal buffer. The CVE record identifies an out-of-bounds write and an unchecked return value. Such memory corruption can crash a process or expose memory; code execution is a possible impact, not an outcome established for every affected system.
Fixes listed in the source 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. These are version-specific fixes, so operators need to check the advisory for their exact platform and distribution.
Updating alone may not change a running service. Processes can continue using the old decoder until restarted, the source says. Node.js applications using built-in fetch may decode Brotli responses automatically; some Python clients do so when a Brotli package is installed. Express and body-parser can also inflate Brotli request bodies in certain versions, but the flaw is in the decoder dependency, not Express itself. A bare Node.js HTTP server does not decode request bodies automatically.
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 Brotli Reaches Many Services
The practical challenge is the decoder’s wide distribution. Brotli is used to compress web traffic, and its C library may be bundled into runtimes and applications or supplied by a system package. The source’s tracker lists more than 30 projects and packages that include their own copies, with seven still unfixed as of October 26, including DuckDB, Apache Arrow’s bundled build, 7-Zip-zstd, p7zip and EDK II firmware tools. Five additional projects were reported fixed in their main development branches, which does not necessarily mean a released version is available.
That spread means a single library update may not cover every deployment. Teams must identify whether their applications use a bundled decoder, a system library, a language package or a runtime-provided copy. They also need to account for containers and long-running processes. A patch that has reached one dependency does not automatically update every image or restart every service.
The risk warrants prompt review, while the available evidence should be described carefully. The source reports that Imperva achieved code execution in a demonstration after several attempts, and the CVE is rated 9.2, Critical, under CVSS 4.0. It also reports that CISA’s data lists exploitation as “none” and that the vulnerability is not in CISA’s Known Exploited Vulnerabilities catalog. That status is not proof that exploitation cannot occur; it describes the reported state at the time of the article.
Products Worth Considering

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

Jackery Explorer 1000 v2 Portable Power Station, 1024Wh LiFePO4 Battery

DJI Mini 4K Drone Combo with 4K Camera, 3-Axis Gimbal, and Two Batteries
As an affiliate, we earn on qualifying purchases.
From Source Fix to Runtime Patches
The source says the underlying Brotli change was committed on February 27, 2026, under the title “Detect and report invalid stream earlier.” It was not identified as a security fix at the time. The releases carrying the correction appeared on October 21, a gap of 236 days, according to the article. The CVE became public on October 22, when a public proof of concept also appeared, the source reports.
That sequence helps explain why exposure can persist across products after a library-level correction. Runtime maintainers, language-package publishers, operating-system distributors and application vendors may each need to incorporate and release the change. The article says that on October 23 some Python package advisories were not yet present in an advisory database, leaving dependency scanners without those entries until GitHub’s advisory was added later that day.
Node.js credits OpenAI Codex Security, and OpenAI said the flaw was found during red-teaming with teams of AI agents. OpenAI also said the February change was not then known to create a security vulnerability and that Brotli had not had a more recent release. These are attributed statements, not independent proof about how the flaw was discovered or why it took months to reach downstream releases.
“The decoder treated one kind of malformed input as “waiting for more data” instead of “this is broken.””
— Node.js project, as described in its advisory cited by ThorstenMeyerAI.com
Which Bundled Copies Remain Exposed
The complete exposure picture is still developing. The source identifies seven bundled copies without fixes on its tracker as of October 26, but that list may change, and the status of a project’s main branch does not confirm a patched release or deployment. Organizations will need to check their own dependency trees, vendor notices and operating-system packages rather than assume that a runtime update covers every copy.
It is also not clear from the supplied material how many systems are exposed, whether attackers have used the flaw outside controlled demonstrations, or whether every reported code-execution path is practical in real deployments. The source states that CISA data shows no known exploitation, but that is a time-specific status, not a guarantee. The article also mentions a separate DreamHost password-reset incident; it says DreamHost named no cause and that nothing links that incident to Brotli.
Patch Releases and Restart Checks
Operators should inventory applications that decode Brotli data, identify the exact library or runtime supplying the decoder, and apply a vendor-supported fixed version. The source’s version list provides starting points, but distribution-specific advisories may identify backported fixes under different package numbers. After updating, teams should restart affected processes and rebuild or redeploy images that contain the vulnerable copy.
Teams should watch for new advisories from maintainers whose bundled copies were still unfixed, and confirm when development-branch changes become released packages. Security monitoring should continue as the public disclosure and proof of concept may prompt further investigation. The supplied source does not give a deadline for remaining projects or a date for a complete inventory, so patch availability and exposure status should be checked against current vendor notices.
Key Questions
What is Broccoli2Shell?
Broccoli2Shell is the name used for the security issue involving CVE-2026-111497, a flaw in Google’s Brotli decoder. The source says malformed compressed input can trigger a write beyond an internal buffer and that code execution was demonstrated on an unmodified Node.js build.
Which versions are affected?
The source identifies Brotli decoder versions 1.0.3 through 1.2.0 as affected. Exposure in a particular application depends on which decoder copy it uses, so operators should check the relevant runtime, package and distribution advisories.
Is there a fix for Node.js?
The listed fixed releases are Node.js 22.23.4, 24.22.1 and 26.12.1. The source says Node.js 20, 23 and 25 do not receive fixes, so users of those lines should consult Node.js guidance for a supported upgrade path.
Why must services be restarted after patching?
A running process may keep the old decoder loaded even after package files are updated. The source advises restarting affected services so they use the patched decoder, and rebuilding or redeploying images where the vulnerable library is bundled.
Has the flaw been exploited in the wild?
The supplied source says CISA data listed exploitation as “none” as of October 26, 2026, and the CVE was not in the Known Exploited Vulnerabilities catalog. It also reports a code-execution demonstration by Imperva. No evidence of real-world exploitation is confirmed in the material, and that status could change.
Source: ThorstenMeyerAI.com
