Skip to content
Reachability Analysis

CVE-2026-111497: Node.js Brotli decoder, is it exploitable where you run it

Code called: openReached: yesControl in front: noExploitation known: yesWalk it through the four questions

What the flaw is

Brotli splits compressed data into blocks, and a block switch says which block type comes next. When a stream declares only one block type for a kind, a switch is not valid and the decoder should reject the stream. The block-switch helper returned a plain boolean, so it gave the same answer for an invalid switch as for a stream that simply ran out of input. The caller was told to send more input. It did, and the decoder kept the extra bytes in an eight-byte internal buffer that never drained. Past the eighth byte the writes land outside the buffer (CWE-252 unchecked return value, leading to CWE-787 out-of-bounds write).

An attacker who can get Brotli data in front of a vulnerable decoder can corrupt process memory. Node.js lists a crash, disclosure of process memory and remote code execution as the outcomes. The bug shipped in Brotli 1.0.3 in March 2018, and the fix was committed upstream on 27 Feb 2026 and released on 21 Oct 2026. Node.js published its advisory and fixed builds on 21 Oct 2026 (the disclosure date on this page); NVD published the record a day later, on 22 Oct 2026. The flaw is in Google's Brotli, so it affects far more than Node.js: any product that embeds the decoder is exposed.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
the Node.js release in use is below the fixed release for its line, or another product embeds a Brotli copy older than 1.0.10, 1.1.1 or 1.2.1Node.js: the fixed releases are in the versions table; end-of-life lines (20.x, 23.x, 25.x and earlier) have no fix. Run node --version on every host, CI runner and developer machine. For container images run docker run --rm <image> node --version. Do not use process.versions.brotli as a test: Node.js cherry-picked the fix without changing the bundled version string, so the value is the same on patched and vulnerable builds of a line (ELLIO read 1.2.0 on builds of both kinds; a 22.x build prints 1.1.0). Compare the Node.js release number instead. A Dockerfile pinned to node:24.22.0 or node:22.23.3 stays vulnerable until the pin moves. Other copies of Brotli: on Linux run ldd $(command -v node) | grep -i brotli; a hit means Node.js links the system library. Then check the package: dpkg -l | grep -i brotli (Debian, Ubuntu), rpm -q brotli (RHEL, Fedora) or apk info -v | grep brotli (Alpine). Debian's tracker records that its nodejs package uses the system Brotli. ELLIO lists fixed distribution packages: Debian bookworm 1.0.9-2+deb12u1, Debian trixie 1.1.0-2+deb13u1, Alpine 1.2.1-r0 (edge, 3.24, 3.23) and 1.1.1-r0 (3.21). For other products, run an SBOM or composition scan for brotli, libbrotli and the language bindings. Examples with published fixed versions (ELLIO): Bun below 1.4.4 (bun --version), PyPI Brotli below 1.2.1 and brotlicffi below 1.2.1.0 (pip show brotli brotlicffi), Envoy where the Brotli decompressor is configured (fixed in 1.40.0, 1.39.3, 1.38.6, 1.37.8, 1.36.12), Ruby brotli gem (0.9.1, 0.9.2). NVD also lists Siemens products as affected; they and their fixed versions are in the versions table.
an attacker can feed it Brotli-compressed input over the networkThree paths reach the decoder. (1) Inbound request bodies sent with Content-Encoding br: run npm ls express body-parser and look for Express 5 or body-parser 2.x, and for Koa with @koa/bodyparser. Per ELLIO, these inflate Brotli bodies before route handlers run. A bare node:http server does not decode request bodies by itself. (2) Outbound responses: built-in fetch(), undici, axios, got and SuperAgent decode Brotli responses, so any fetch to a URL an attacker influences counts (webhooks, link previews, crawlers). (3) Direct calls: grep -rn "brotliDecompress\|createBrotliDecompress" . in your code and dependencies. Then check which services accept requests from untrusted networks, and whether your proxy or load balancer forwards Content-Encoding br to the application. Test your own staging service with a harmless Brotli body and read how it responds. Inventory features that fetch user-supplied URLs.

Affected and fixed versions

Node.js releases are from the 21 Oct 2026 security release. Newer patch releases of the same lines also carry the fix. Siemens rows come from the NVD record for this CVE.
Product lineAffected versionsFirst fixed version
Node.js 26.xBefore 26.12.126.12.1
Node.js 24.xBefore 24.22.124.22.1
Node.js 22.xBefore 22.23.422.23.4
Node.js 25.x, 23.x, 20.x and earlier (end of life)All versions (Node.js: end-of-life versions are always affected)No fix, move to a supported line
Google Brotli 1.0.x1.0.3 up to but excluding 1.0.101.0.10
Google Brotli 1.1.x1.1.0 up to but excluding 1.1.11.1.1
Google Brotli 1.2.x1.2.0 up to but excluding 1.2.11.2.1
PyPI Brotli and brotlicffiBrotli 1.0.3 up to but excluding 1.2.1; brotlicffi 1.0.3 up to but excluding 1.2.1.01.2.1 and 1.2.1.0
Siemens products with a fixed version in NVDCloud Connector Configurator before V1.24.3; Data Flow Monitoring before V3.0.18; Databus Configurator before V4.0.1; DataXess Configurator before V1.5.7; Edge OPC UA Server Configurator before V2.3.10; Flow Creator Configurator before V1.15.1; Gridscale X DSA V5.3, fixed in V5.4; Gridscale X PSS®E before V36.8.0; SIMATIC BRAUMAT and SIMATIC SISTAR V8.2 Update 1 up to before V8.2 Update 5; SIMATIC WinCC OA V3.20 before V3.20.17.1; SIMATIC WinCC OA V3.21 before V3.21.7; User Management Component (UMC) before V2.15.4.1The version NVD names as the upper bound (for example V1.24.3 for Cloud Connector Configurator); newer releases carry the fix
Siemens products NVD lists as affected with no fixed versionDesigo CC V8 and V9, Industrial Edge Hub, Industrial Edge Management Cloud, Common Configurator (CC on IEM and CC on Edge), Insights Hub, Integrated PA Suite Tester, SENTRON Powermanager V8 and V9, SICAM PAS CC V6.02, SICAM SCC V7.01, HyperLynx, Innexis Architecture Native Acceleration 2026, PADS Pro Essentials, Student Edition and Professional, PAVE360 Automotive 2026, Xpedition Designer and Enterprise, Simcenter Executable Digital Twin and Studio, Process Preparation X, Teamcenter V2412, V2506, V2512 and V2606, Opcenter Connect Electronics and MOM, Opcenter Execution Core, Discrete, Foundation, Pharma and Process, Opcenter Intelligence, Intra Plant Logistics, Quality, RDnL and X, COMOS Walkinside, Project Server Web Administration Tool, SIMATIC Profiling Tool, WinCC Companion, WinCC Runtime Professional, WinCC Unified for Industrial Edge, WinCC Unified PC Runtime, WinCC Unified SIQENCE, WinCC V7/V8, and TIA AdministratorNone named: ask Siemens support for patch status

If the fix cannot go in yet

  • Upgrade Node.js to the fixed release for your line in the versions table (or a newer patch release of the same line), then rebuild images and restart processes. Cost: a rebuild and redeploy. Node.js 20.x, 23.x and 25.x get no fix, so those need a move to a supported line.
  • Upgrade every other copy of Brotli: Google Brotli 1.0.10, 1.1.1 or 1.2.1, the distribution package where Node.js links the system library, Bun 1.4.4, PyPI Brotli 1.2.1. A Node.js upgrade fixes only the copy Node.js bundles.
  • The Node.js advisory lists no workaround. Stopgap from the researchers at Aikido and ELLIO: reject inbound requests with Content-Encoding br at the reverse proxy, load balancer or application middleware. Cost: clients that send Brotli-compressed request bodies get an error. This does not cover Brotli responses your own application fetches from other servers.
  • Vercel added firewall rules on 21 Oct 2026 that block the attack in inbound requests (reported by Aikido). Cost: none for Vercel-hosted apps; the rules cover inbound requests only.
  • CISA's KEV required action: apply mitigations per vendor instructions in line with BOD 26-04, or stop using the product if mitigations are unavailable. The KEV due date was 10 Nov 2026.

What to look for

  • A failed attack against a patched build is rejected with ERR__ERROR_FORMAT_BLOCK_SWITCH (decoder error code -17) and a 400 response, per ELLIO. Search application logs for that string.
  • A failed attack against a vulnerable build often crashes the worker. Look for repeated Node.js process crashes or restarts, and for requests with Content-Encoding br just before them. On hosts with systemd-coredump, check /var/lib/systemd/coredump: ELLIO notes each crash can write a core file that holds credentials from other users' sessions, so limit who can read those files and how long you keep them.
  • Some other decoders (Python Brotli 1.2.0, brotlicffi 1.2.0.0, the PHP extension streaming API, the Ruby gem) return no bytes, never finish and never raise an error. Look for requests that hang with a CPU at 100 percent (ELLIO observed this in PHP).
  • Network indicators published by ELLIO: scanner user agent Mozilla/5.0 (compatible; node2shell-check/1.0) from AS44620 (sends 20 POST bodies with Content-Encoding br in two bursts after a GET to /); exploit traffic on 26 Oct 2026 from 94[.]154[.]43[.]7 carrying a 23,069,983-byte Brotli request body aimed at Node.js v24.22.0 on x86-64 (SHA-256 7fcbdaaecd4419e2930927844f3b772668204737a4e7602a2290c991c93c5c4b).
  • If a vulnerable, internet-reachable service saw such traffic or unexplained crashes, treat the host as possibly compromised and follow your incident process. CISA's KEV entry sets forensic triage to No for this CVE, so no BOD 26-04 triage steps are mandated for it.

Exploited 5 days after disclosure: disclosed 21 Oct 2026, first exploitation reported 26 Oct 2026.

Exploitation reported so far

CISA added the CVE to KEV on 27 Oct 2026. The first public report of exploitation in the wild is from ELLIO: its sensors recorded a Brotli request body aimed at Node.js v24.22.0 on x86-64 on 26 Oct 2026 at 15:08 UTC, from 94[.]154[.]43[.]7. ELLIO says the delivery layer copies public proof-of-concept code and the final stage is new, and that its own test of this chain gave no shell in 50 attempts. ELLIO had seen the scanner node2shell-check probe for Brotli decoding the day before.

Public exploits depend on the exact Node.js build, because they use fixed memory offsets for one binary and predictable socket numbers. Most failed attempts crash the worker, so even unsuccessful attacks cause denial of service. Aikido noted on 22 Oct that no exploitation in the wild had been reported yet. KEV does not know of ransomware use (Unknown).

Why static reachability settles it

Whether a vulnerable decoder runs on attacker-influenced data is a question about versions and code paths: which Node.js or library build you run, and which routes decompress request bodies or fetch outside URLs. Static inventory answers both. KEV tells you attackers are active, but only the inventory tells you which of your services can be hit. See static reachability for what the method proves and misses.

Sources

  1. CVE-2026-111497: NVD record, read 19 Nov 2026
  2. CVE-2026-111497: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-111497: vendor advisory (Node.js security releases, 21 Oct 2026), read 19 Nov 2026
  4. CVE-2026-111497: Google Brotli 1.2.1 release notes (upstream fix release), read 19 Nov 2026
  5. CVE-2026-111497: GitHub advisory API record for the Brotli flaw (GHSA-9v8h-qqgm-4m35), read 19 Nov 2026
  6. CVE-2026-111497: ELLIO research on exploitation and affected builds, read 19 Nov 2026
  7. CVE-2026-111497: Aikido analysis and fix guidance, read 19 Nov 2026
  8. CVE-2026-111497: oss-security mailing list post (23 Oct 2026), read 19 Nov 2026

Last reviewed 19 Nov 2026.