The Broccoli2Shell Compression Bug: Questions For Your Engineering Team
AIThis post was created with the assistance of artificial intelligence (AI).

🔍 Read the full analysis: The Broccoli2Shell Compression Bug: Questions For Your Engineering Team on ThorstenMeyerAI.com

Buying for a business?Offer from Amazon

Get business pricing on office and shipping supplies

  • Business-only prices and quantity discounts
  • Tax-exempt purchasing
  • Multiple users, one account, clear invoices
As an affiliate, we earn on qualifying purchases.

TL;DR

CVE-2026-111497 is a memory-corruption flaw in Google’s Brotli C decoder that affects versions 1.0.3 through 1.2.0 and is present in several runtimes and bundled copies. Patches are available for major products, but teams must identify their actual Brotli dependencies and restart affected processes; the supplied reporting says there is no confirmed in-the-wild exploitation.

CVE-2026-111497, a flaw in Google’s Brotli C decoder, is prompting patch reviews across Node.js, Python and other software that includes the compression library. The vulnerability affects decoder versions 1.0.3 through 1.2.0; fixes are available for multiple releases, but teams must check whether their applications or dependencies bundle a vulnerable copy and restart running processes after updating.

The flaw involves malformed compressed input that the decoder can treat as incomplete rather than invalid. The Node.js security advisory describes the result as an out-of-bounds write: the decoder can write beyond an eight-byte internal buffer. Such memory corruption can cause a crash or memory exposure and, under some conditions, may permit code execution. The CVE record lists an out-of-bounds write and an unchecked return value. These are technical risk descriptions, not evidence that every affected deployment can be exploited in the same way.

The supplied report says Google’s CVE record assigns the vulnerability a CVSS 4.0 score of 9.2, Critical. Imperva reported running code on an official Node.js image after several attempts. That demonstration is distinct from evidence of attacks against systems in ordinary use: the report says CISA’s data lists exploitation as “none” and the CVE is not in the agency’s Known Exploited Vulnerabilities catalog.

Fixed releases 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; Bun 1.4.4; and updates for Envoy, Istio, .NET and Debian. Node.js 20, 23 and 25 are listed as receiving no fix. The report also says seven tracked bundled copies remain unfixed as of October 26, including copies associated with DuckDB, Apache Arrow and firmware tools.

At a glance
reportWhen: Developing; reported October 26, 2026
The developmentA Brotli decoder vulnerability disclosed in October has prompted security fixes across runtimes and packages, while some bundled copies remain unpatched.
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 Copies Matter

One decoder can reach many systems because software often ships or depends on Brotli indirectly. Node.js can decode Brotli responses through its built-in fetch function. Python HTTP clients may decode them when a Brotli package is installed, while services that accept compressed request bodies can expose other paths. File-processing tools may use the same C decoder for archives, fonts, data files or firmware.

This makes an inventory of direct dependencies insufficient. A team could update its application framework yet still run a vulnerable decoder supplied by a runtime, operating-system package, container base image or separate tool. The report specifically notes that upgrading Express alone does not fix this flaw: the issue is in Brotli, not Express. Exposure also depends on whether the affected component processes attacker-controlled compressed data and how that component is configured.

For engineering and security teams, the practical issue is supply-chain reach and patch timing. A library fix must pass through upstream projects, package maintainers, distributions and deployment images before it reaches live processes. Until that chain is checked, a patched top-level dependency does not establish that a service is no longer using an affected decoder.

Breville Barista Express Espresso Machine with Grinder, Black Truffle

Breville Barista Express Espresso Machine with Grinder, Black Truffle

As an affiliate, we earn on qualifying purchases.

From Source Fix to Runtime Patches

The report traces the underlying source-code change to February 27, 2026. It says the commit was titled “Detect and report invalid stream earlier” and did not identify the change as security-related. Releases containing the fix appeared on October 21, a reported gap of 236 days. OpenAI said the vulnerability was not known at the time of the commit and that Brotli had not had a more recent release.

The CVE became public on October 22, and the report says a proof of concept appeared on GitHub that day. Subsequent fixes have been issued across runtimes and packages. This chronology matters because applications can depend on independently maintained copies: an upstream correction is not automatically present in every product that incorporates the library.

The report links the discovery to AI-assisted security work, saying Node.js credited OpenAI Codex Security and OpenAI described finding the flaw during red-teaming with teams of AI agents. It also compares the breadth of affected software to other widely reused parsing libraries. Those descriptions provide context, but they do not change the technical scope established by each product’s own advisory.

Exposure and Exploitation Still Unclear

The supplied reporting identifies no confirmed in-the-wild exploitation as of October 26, 2026. That status does not establish that no attempts have occurred; it reflects the cited CISA data and the absence of the CVE from the agency’s known-exploited catalog. Imperva’s reported code-execution demonstration shows a possible outcome in a test, not a confirmed attack on a production system.

The exact exposure of any organization remains dependent on its software versions, build choices and data flows. Some products bundle Brotli, while other builds use an operating-system library. The report lists projects with unfixed copies but does not establish which deployments are exposed or whether those projects have since issued updates. It also does not give a complete, independently verified inventory of every affected product.

A separate report about DreamHost resetting some email and FTP/SFTP passwords is not linked to this vulnerability in the supplied material. DreamHost reportedly gave no cause, so the password resets should not be presented as evidence of a Brotli-related incident.

Patch, Rebuild and Restart

Engineering teams should first identify which services and tools process Brotli-compressed responses, request bodies or files, then check the precise runtime, package and operating-system versions against vendor advisories. Where a fixed release is available, teams should update the relevant component, rebuild affected images and deploy the new artifacts. The report warns that running processes retain the old decoder until restarted, so updating files or packages without restarting may leave existing services on vulnerable code.

Teams using products with no listed fix should monitor their maintainers’ advisories and consider whether the affected functionality can be limited while awaiting an update. They should verify whether their distribution links against a system Brotli library or includes its own copy, and confirm the patch in the deployed build rather than relying only on a dependency manifest.

The next developments are expected to come through package, runtime and distribution advisories as remaining bundled copies receive fixes. The source report’s tracker listed seven unfixed copies on October 26 and five additional projects with fixes in their main branches. Those statuses can change, so teams should recheck maintainers’ release notes and security notices before treating their inventories as current.

Key Questions

What is CVE-2026-111497?

It is a memory-corruption vulnerability in Google’s Brotli C decoder, reported as affecting versions 1.0.3 through 1.2.0. Malformed compressed input can cause an out-of-bounds write.

Does every Node.js application need to update?

Teams should check the exact Node.js version and how it was built. The report lists fixes in 22.23.4, 24.22.1 and 26.12.1, and says Node.js 20, 23 and 25 receive no fix. Some distributions use a system Brotli library, so the relevant package may differ from an official Node.js build.

Will updating a package protect an already-running service?

Not necessarily. The report says a running process keeps its old decoder until it restarts. Teams should deploy the fixed component and restart affected processes, then verify the version in the live environment.

Has the flaw been exploited in the wild?

The supplied report says CISA’s data lists exploitation as “none” and that the CVE is not in its Known Exploited Vulnerabilities catalog. It also describes an Imperva code-execution demonstration. Those facts do not confirm attacks against production systems, and the absence of a listing does not prove no attempts have occurred.

Is the DreamHost password reset connected to this bug?

No connection is established in the supplied reporting. DreamHost reportedly named no cause for its email and FTP/SFTP password resets, and the report says nothing links the incident to Brotli.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

Ezb Neue Banknoten

Die Europäische Zentralbank plant die Einführung neuer Euro-Banknoten. Details zu Design, Zeitplan und Bedeutung sind noch unklar.

The 9 Most Efficient AI Student Apps For 2026

Discover the nine most effective AI-powered student apps for 2026, enhancing learning, organization, and productivity with advanced features and ease of use.

10 Best Computers, Tablets & Components For Flexible Work In 2026

Discover the 10 best computers, tablets, and components for flexible work in 2026, based on latest expert evaluations and user needs.

デジタル・リアルティ、シンガポールで50MW規模の新規データセンター開発事業に選定される

Digital Reality has been chosen to develop a 50MW data center in Singapore, marking a significant expansion in Southeast Asia’s digital infrastructure.