Node.js Brotli Flaw (CVE-2026-111497): Corrupt Decompression Data Can Reach Memory Corruption and RCE

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

Node.js Brotli Flaw (CVE-2026-111497): Corrupt Decompression Data Can Reach Memory Corruption and RCE

Decompression is one of those operations that feels too boring to be dangerous. CVE-2026-111497 is the correction: an out-of-bounds write in the Brotli decoder bundled with Node.js, where a malformed compressed stream doesn't just fail — it keeps writing. Per Node.js's own advisory wording, an attacker who can supply Brotli data that an application decompresses with node:zlib can corrupt process memory, which "can lead to a crash, disclosure of process memory, or remote code execution."

What Happened

The flaw shipped in Node.js's October 2026 security release (October 21) — ten fixes in total, with this one rated High by the Node.js project.

Am I Affected?

Two questions decide it:

  1. Which Node runtime are you on? node --version — anything on the 22/24/26 lines below the fixed releases carries the vulnerable decoder. (Your runtime version is, correctly, not something an outside scanner can see — check it where the app runs.)
  2. Does your app decompress Brotli data it doesn't fully control? Upload pipelines, proxy and cache layers, webhook and feed ingestion, archive handling — anywhere node:zlib's Brotli decompression touches bytes an attacker can influence. Brotli compression of your own responses is not the exposed path; decompression of supplied data is.

Both yes means this is a patch-now item: memory corruption in a network-facing runtime is the class of bug that turns into RCE with enough attacker patience.

What To Do Now

  1. Update Node.js to 26.12.1, 24.22.1, or 22.23.4 (or the current release on your line), and redeploy — runtime CVEs don't patch themselves through npm update, because the vulnerable code is in the runtime, not in a dependency.
  2. Audit decompression call sites for attacker-controlled input, and put size limits in front of them regardless; decompression endpoints are also where zip-bomb style denial of service lives.
  3. Check your other runtimes too. The same upstream Brotli flaw touched PHP and anything else bundling the library — a week like this one is a good prompt to inventory where Brotli shows up in your stack at all.

The durable lesson for AI-built apps: your dependency tree gets scanned, audited, and blogged about — your runtime usually doesn't. Node, PHP, and Python release security fixes on their own cadence, and "the app works" tells you nothing about which decoder version is sitting underneath it. Put runtime versions on the same patch list as packages.

The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.

New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.

Check your own app — free, in about a minute.

The free mini-scan checks your live homepage for TLS/HTTPS basics, response security headers, cookie flags, exposed sensitive files, Firebase/Supabase backend rules, and the WordPress plugin versions your site exposes. You get a score and the finding titles — no account, no card.

Run the free mini-scan →

← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report