No attacks reportedCVE published · 22 Oct 2026
Node.js
CVE-2026-111497 Severity · Critical
CVSS 9.2
Affected
Node.js 22.x below v22.23.4, 24.x below v24.22.1, 26.x below v26.12.1, all End-of-Life lines such as 20.x and 25.x; Google Brotli 1.0.3 to 1.2.0
Fixed in
Node.js v22.23.4, v24.22.1, v26.12.1; Google Brotli 1.0.10, 1.1.1, 1.2.1

CVE alert · Node.js and JavaScript

CVE-2026-111497: a Brotli bug in Node.js lets an attacker overwrite server memory

An attacker who can send Brotli-compressed data to a Node.js app that unpacks it can corrupt its memory and possibly run their own code. The bug affects versions 22.x, 24.x, 26.x and older ones that no longer get updates. Install a fixed release today.

Check your systems with your AI agent

Paste this prompt into an AI agent that can run commands on your machines. It only reads versions and settings, asks before using administrator rights, and ends with a report.

Check whether my systems are affected by CVE-2026-111497 in Node.js, then write me a report.

Read the alert first: https://securityaudit.ae/cve/cve-2026-111497-nodejs-brotli/

What the alert says (facts checked 23 October 2026):
- Affected: Node.js 22.x below v22.23.4, 24.x below v24.22.1, 26.x below v26.12.1, all End-of-Life lines such as 20.x and 25.x; Google Brotli 1.0.3 to 1.2.0
- Fixed in: Node.js v22.23.4, v24.22.1, v26.12.1; Google Brotli 1.0.10, 1.1.1, 1.2.1
- Exploited: No attacks reported as of 23 October 2026

Rules:
- Read only. Do not install, update, restart, delete or change anything, and never run exploit or proof-of-concept code.
- Run only commands that read versions or settings. Ask me before any command that needs sudo or administrator rights.
- If you do not know which machines, containers, cloud accounts or sites are in scope, ask me for the list before you start.
- If a machine cannot be reached or a command fails, say so. Do not guess.

Steps:
1. Find where Node.js runs: servers, containers and their hosts, cloud services, sites.
2. On each one, read the installed version and the settings the alert names. The alert gives these commands:

    node --version

    docker run --rm --entrypoint node <your-image> --version

3. Compare each version with the affected and fixed versions above. When a vendor or a distribution ships its own fixed package, the alert names it.
4. Report: one line per machine or service with the version found, Affected, Not affected or Unknown, and the evidence (the command and its output). Then the actions to take, in order, from the alert's "How to fix" section, and what you could not check.

Key facts

FactDetail
ProductNode.js (JavaScript runtime) and Google Brotli (compression library)
Affected versionsNode.js 22.x below v22.23.4, 24.x below v24.22.1, 26.x below v26.12.1, all End-of-Life lines such as 20.x and 25.x; Google Brotli 1.0.3 to 1.2.0
Fixed inNode.js v22.23.4, v24.22.1, v26.12.1; Google Brotli 1.0.10, 1.1.1, 1.2.1
Severity9.2 Critical (CVSS 4.0, Google)
Who can attackA remote attacker with no login, if the app unpacks Brotli data the attacker supplies
ExploitedNo attacks reported as of 23 October 2026
CVE published22 October 2026

What an attacker can do

Brotli is a format that shrinks data before it travels over a network. Node.js ships with a copy of Google's decoder for it (the code that unpacks the data). Your apps reach it through the node:zlib module.

The decoder mishandles one kind of broken input. It reports that it needs more data, when it should report a format error. So it keeps adding input bytes to a fixed 8-byte area of memory until they run past its end. This is an out-of-bounds write.

The Node.js project says this can crash your app. It can also expose the app's memory, which holds whatever the app is handling, such as customer records or secret keys. In the worst case it can lead to remote code execution (the attacker runs their own code on your server). From there they can read your data and change your site.

Who is affected

The bug affects Node.js 22.x, 24.x and 26.x before the fixed releases. The project says End-of-Life lines (older versions that no longer get security fixes) are always affected. That covers 20.x (ended 30 April 2026) and 25.x (ended 1 June 2026).

No login is needed. Google's CVSS score (the standard 0 to 10 severity rating) marks the attack as needing a condition outside the attacker's control. It does not say what that condition is. Separately, the Node.js advisory says the attacker must be able to supply Brotli data that your app unpacks with node:zlib. Search your code and packages for:

  • zlib.brotliDecompress
  • zlib.brotliDecompressSync
  • zlib.createBrotliDecompress

The built-in fetch() also unpacks Brotli responses (Content-Encoding: br) automatically, so fetching URLs an outsider controls exposes your app. So does new DecompressionStream('brotli'). Search again without the zlib. prefix: some code calls these functions by name alone.

Google's Brotli library, which other software also uses, has the same bug in versions 1.0.3 through 1.2.0.

How to check your version

Run this on each server:

shell
node --version

You are exposed if it prints a 22.x version below v22.23.4, a 24.x below v24.22.1 or a 26.x below v26.12.1. Any 20.x, 25.x or older version is exposed too.

For a Docker image, run node inside it:

shell
docker run --rm --entrypoint node <your-image> --version

--rm deletes the test container when it exits. --entrypoint replaces the image's start command with node.

Do not rely on npm ls here: the decoder is not a package it can see. The official binaries and node Docker images carry their own copy, so for them only the Node.js version you run matters.

On Debian and Ubuntu, the nodejs package uses the system Brotli library instead. As of 23 October 2026, neither has shipped a fixed libbrotli1 (Debian: all releases vulnerable, bug 1151690; Ubuntu: needs evaluation). A server that runs this nodejs package stays exposed after apt upgrade. Until a fix ships, move that server to the official Node.js binaries (v22.23.4, v24.22.1, v26.12.1) or a node Docker image. Update libbrotli1 once either distribution publishes a fixed package.

Alpine's main nodejs package also uses the system library: update brotli-libs to 1.2.1-r0 (edge, 3.24, 3.23) or 1.1.1-r0 (3.21, 3.22). On the edge branch, the nodejs-current package carries its own copy, so update it to 26.12.1-r0.

What to do now

  1. Update Node.js to v22.23.4, v24.22.1, v26.12.1 or a later release on the same line. All three came out on 21 October 2026. Updating npm packages does not fix it. The decoder lives inside the node binary, or in the system Brotli library for Debian, Ubuntu and Alpine nodejs packages. On Alpine, also update brotli-libs. Debian and Ubuntu have no fixed libbrotli1 yet: move those servers to the official binaries or a node Docker image.
  2. Rebuild your Docker images from a fixed base image, such as node:22.23.4 in your Dockerfile's FROM line. Then redeploy every container: a running container keeps its old node program.
  3. Move servers off 20.x and 25.x: Node.js shipped no fix for them.
  4. Update any other Brotli library or binary in the 1.0.3 to 1.2.0 range to 1.0.10, 1.1.1 or 1.2.1.

As of 23 October 2026, Node.js and Google have published no way to block the attack without updating, and no signs of compromise. No one has reported an attack, and the flaw is not in the CISA KEV catalog (the US list of flaws known to be used in attacks).

Get help

Updating closes this flaw. Flaws in your own code get no CVE and no update, and a test of your app is how they are found.

Web app and API security test

A penetration test of your web app and its API: who can see whose data, and what an attacker can change.

From AED 20,000, excl. 5% VAT

Ask for a quote Book a call

Sources

  1. CVE-2026-111497 record CVE Program
  2. Wednesday, October 21, 2026 Security Releases Node.js project
  3. Brotli v1.2.1 release (also v1.1.1, v1.0.10) Google (google/brotli on GitHub)
  4. CVE-2026-111497 in the Debian security tracker Debian Security Team
  5. CVE-2026-111497 Canonical (Ubuntu Security)
  6. Known Exploited Vulnerabilities Catalog CISA

The same update also fixes CVE-2026-105482, CVE-2026-105483, CVE-2026-106069, CVE-2026-105481, CVE-2026-106072, CVE-2026-106074, CVE-2026-106070, CVE-2026-106071, CVE-2026-106073.

More CVE alerts

All CVE alerts