Most teams will first hear about CVE-2026-111497 as "a Node.js thing". It is wider than that, and the way it spreads is worth understanding before you triage.
What it is
According to The Hacker News, the flaw is a memory-corruption bug in Google's Brotli decoder: crafted compressed data can write past the end of a buffer, leading to a crash, a leak or attacker-controlled code. Google rates it 9.2 on CVSS 4.0, Node.js calls it high, and Red Hat scores it 8.1. Fixes landed on 21 October, with other vendors following product by product.
The detail that stands out is the timeline. The same report says the fix went into Brotli's source on 27 February, but no release carried it until October, and that OpenAI's team described the root cause as fixed earlier without realising it was a security issue. Anyone pinned to a released version stayed vulnerable for eight months while a patch sat in the repository.
Who is exposed
- Node.js 22.x, 24.x and 26.x before 22.23.4, 24.22.1 and 26.12.1, when
fetch()reads abrresponse or Express 5 / body-parser 2 unpacks a Brotli request body. Older, end-of-life lines get no fix. - Bun 1.4.3 and earlier; fixed in 1.4.4.
- Python
Brotliandbrotlicffi1.2.0 and earlier, fixed in 1.2.1 and 1.2.1.0. Here installation alone is the risk: requests, urllib3, httpx and aiohttp will decode Brotli responses even if your code never imports it. - Envoy and Istio, only where Brotli decompression is switched on.
It works in both directions. A malicious server can hit an unpatched client, and a malicious client can hit an unpatched server, which is why outbound calls to third-party APIs matter as much as your own endpoints.
How worried to be
Not panicked, but not relaxed. A separate piece from The Hacker News on Node2Shell says Imperva's team ran code on an unmodified Node.js 24.22.0 build for Linux arm64, and that 24.22.1 rejected the same data. The exploit needed several attempts, has not been released and was not shown on other software. No in-the-wild exploitation has been reported. That is a head start, not a reprieve.
What to do this week
- Update the runtime, then restart. A running process keeps the old decoder in memory, and container images need rebuilding.
- Check Python environments by installed version, not by scanner alert. The report notes the CVE record points at Google's repository, so the GitHub advisory initially listed no affected package and Dependabot-style tools may stay quiet. PyPI advisories were added on 23 October.
- If you cannot patch Node yet, there is no published workaround. For Python you can uninstall the two Brotli packages so clients fall back to gzip and deflate. Dropping
brfromAccept-Encodingdoes not help, because servers can send it anyway. - Find the quiet users: service meshes, API gateways, scanners and CLI tools that bundle their own runtime.
The wider lesson
A "fixed upstream" note in a changelog is not a deployable fix. Ask suppliers when a fix becomes a release, and keep a list of what you ship that embeds someone else's decoder. We help UK teams build that inventory and a patch path to match: sales@halfteck.com.