Broccoli2Shell: How To Review Your Runtime And Dependency Footprint
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: Broccoli2Shell: How To Review Your Runtime And Dependency Footprint on ThorstenMeyerAI.com

Before you orderOffer from Amazon

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
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

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 prompted fixes across Node.js, Python and other platforms. The source says a fix was committed in February but released in October; security teams still need to find bundled copies and restart patched processes. The vulnerability is rated Critical, but the cited CISA data reports no known exploitation.

CVE-2026-111497, a flaw in Google’s Brotli decoder, has triggered security fixes across software runtimes and packages after researchers demonstrated memory corruption and code execution in an unmodified Node.js build. The vulnerability affects Brotli versions 1.0.3 through 1.2.0; the available fixes now span Node.js, Python packages, Bun, Envoy, Istio, .NET and some Linux distributions.

The flaw occurs when the decoder handles malformed compressed input as though it is incomplete. According to the Node.js security advisory, this can cause data to be appended beyond an internal eight-byte buffer. The resulting memory corruption can crash a process or, under some conditions, expose memory or allow code execution. The CVE record identifies an out-of-bounds write and an unchecked return value. The fix makes the decoder reject the malformed stream with a format error.

Imperva demonstrated code execution on an official Node.js image after several attempts, according to the source report. That is evidence of a demonstrated attack scenario, not confirmation of attacks in the wild. The report says the CVE has a CVSS 4.0 score of 9.2; CISA’s data lists exploitation as “none,” and the vulnerability is not in CISA’s Known Exploited Vulnerabilities catalog.

Published fixes 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 updates for Envoy, Istio and .NET. Affected Node.js branches 20, 23 and 25 have no fix listed in the source. Teams should check each product’s advisory and support status rather than assume every version can be patched.

At a glance
reportWhen: Developing as of October 26, 2026
The developmentA critical Brotli decoder vulnerability has prompted patches across multiple runtimes and packages, widening the response beyond Node.js.
Thorsten Meyer AI
CVE-2026-111497 · 26 Oct 2026

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.

9.2CVSS 4.0, Critical, in Google's CVE record
1.0.3–1.2.0affected Brotli versions
3supported Node.js lines fixed on 21 Oct
~83 MPyPI downloads of Brotli in the last month

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 .br files (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

ComponentFixed inNote
Google Brotli (C library)1.0.10 · 1.1.1 · 1.2.11.0.3–1.2.0
Node.js22.23.4 · 24.22.1 · 26.12.120, 23, 25: no fix (end of life)
Python Brotli / brotlicffi1.2.1 / 1.2.1.01.0.3 up to 1.2.0.x
Bun1.4.4includes Brotli 1.2.1
Envoy Proxy1.40.0 · 1.39.3 · 1.38.6 · 1.37.8if Brotli decompression is configured
Istio1.29.9 · 1.30.6 · 1.31.21.29 is end of life
.NET runtime8.0.33 · 9.0.22 · 10.0.14GitHub source builds still affected
Debian brotlibookworm 1.0.9-2+deb12u1 · trixie 1.1.0-2+deb13u1DLA 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 Bundled Decoders Matter

The risk extends beyond applications that directly call Brotli. A runtime or package may include its own copy of the decoder, while another may link to a system library. That makes a single low-level parsing flaw relevant to web services, proxies, data tools and other software that processes compressed responses, request bodies or files.

Exposure depends on how a system uses Brotli. The source identifies automatically decoded web responses and accepted compressed request bodies as possible routes, alongside files processed by tools using the C decoder. A bare Node.js HTTP server does not automatically decode request bodies, and upgrading Express alone does not fix a flaw in the Brotli library it uses. Teams need to trace the actual decoder and data flow, not just search for a particular framework.

The response also has a process-level catch: replacing a package does not update a decoder already loaded by a running process. The source advises restarting after patching. For operators, the work may involve application dependencies, container images, operating-system packages and services that were built with bundled copies.

Products Worth Considering

Bose QuietComfort Wireless Noise Cancelling Headphones - Twilight Blue Limited Edition

Bose QuietComfort Wireless Noise Cancelling Headphones – Twilight Blue Limited Edition

Jackery HomePower 3600 Plus Portable Power Station, 3584Wh, 3600W

Jackery HomePower 3600 Plus Portable Power Station, 3584Wh, 3600W

As an affiliate, we earn on qualifying purchases.

From Source Fix to Runtime Patches

The source report traces the underlying code change to February 27, 2026, when a Brotli commit titled “Detect and report invalid stream earlier” was made. It says the commit did not identify a security issue. The releases carrying the fix appeared on October 21, a gap of 236 days. OpenAI said the vulnerability was not known at the time of the commit and that no newer Brotli release was available.

The CVE became public on October 22, and the source says a public proof of concept appeared that day. Fixes then had to move through software that bundles Brotli: library releases, language runtimes, packages, distributions and container images. The report says some Python packages were not listed in advisory databases on October 23, limiting what dependency scanners could flag at that point; GitHub’s advisory added them later that day.

The source attributes discovery to AI-assisted security work: Node.js credits OpenAI Codex Security, and OpenAI said it found the flaw during red-teaming with teams of AI agents. That describes the reported discovery process; it does not establish that every affected product or bundled copy has been identified. As of October 26, the cited tracker lists seven bundled copies still unfixed, including copies associated with DuckDB, Apache Arrow, 7-Zip-zstd, p7zip and EDK II firmware tools.

Remaining Exposure Across Bundles

The full set of affected software is still developing. The source tracker lists more than 30 projects and packages with bundled copies, but says seven remained unfixed as of October 26 and five others had fixes in their main branches. A fix in a project’s main branch may not yet be present in a released version. The status can change as maintainers publish updates.

The cited data does not establish whether attackers have used the flaw outside demonstrations. CISA’s exploitation field is reported as “none,” but that is not proof that exploitation is impossible or that every incident has been ruled out. The source also does not provide a complete inventory of affected deployments or establish that all listed routes are reachable in every product.

Organizations should confirm which decoder their builds use, whether the affected code is reachable, and whether a vendor update is available. The source mentions DreamHost password resets after a separate incident but names no cause; it explicitly provides no evidence linking that incident to Brotli.

Patch, Rebuild and Restart

Security and platform teams should check vendor advisories and dependency inventories for Brotli 1.0.3–1.2.0 and affected runtime or package versions. They should update supported components, rebuild images where bundled libraries are included, and restart services so patched code is loaded. Where a project has only fixed its main branch, teams should watch for a tagged release before treating the deployed copy as updated.

Organizations should also review whether applications automatically decode Brotli responses, accept compressed request bodies, or process files through affected libraries. Dependency scanners can help, but the source’s account of delayed advisory listings shows why a clean scan alone may not settle the question. Maintainer advisories and the actual build configuration remain relevant checks.

Further updates are expected as projects with outstanding bundled copies publish releases and as distributions ship packages. The immediate status to track is which deployed copies have received a released fix and been restarted; the source’s tracker is dated October 26, 2026, and may no longer reflect later releases.

Key Questions

What is Brotli2Shell?

Brotli2Shell is the name used for a security flaw in Google’s Brotli decoder, tracked as CVE-2026-111497. The source says malformed compressed input can cause an out-of-bounds write and memory corruption; code execution was demonstrated in an official Node.js image.

Which versions are affected, and what is fixed?

The source identifies Brotli 1.0.3 through 1.2.0 as affected. Listed fixes include Brotli 1.0.10, 1.1.1 and 1.2.1, plus updated releases for Node.js, Python packages, Bun, Envoy, Istio, .NET and some Linux distributions. Check the relevant vendor advisory for your exact product.

Is the vulnerability being exploited in the wild?

The source reports a code-execution demonstration by Imperva, but says CISA’s exploitation data lists “none” and the CVE is not in CISA’s Known Exploited Vulnerabilities catalog. That does not establish that every possible attack has been ruled out.

Is updating a dependency enough?

Not necessarily. Some products bundle their own Brotli copy, and a running process can continue using the old decoder after files are updated. Check the deployed build, install an applicable fix, rebuild bundled components when needed, and restart affected processes.

Source: ThorstenMeyerAI.com

You May Also Like

What The Claude Fuzz-Test Project Shows—and What It Cannot Show

Anthropic and Theorem report machine-checked proofs for 239 fuzz-test entry points, while warning the results cover narrow, modeled conditions.

Windows 11½

Search and coverage interest in “Windows 11½” is spiking, but the cause is unconfirmed and no specific announcement is verified.

Anthropic’s ‘Claude-led’ CRISPR-like Discovery Is Sparking Controversy – WCPO 9 News

A WCPO 9 headline reports controversy over an alleged Claude-led CRISPR-like discovery, but available material does not identify the finding or dispute.

Google Strengthens AI & Economy Division With Fresh Talent

Google has appointed top economists and researchers to its AI & Economy program, aiming to study AI’s impact on productivity, labor, and scientific discovery.