Key facts
| Fact | Detail |
|---|---|
| Product | Node.js (JavaScript runtime) and Google Brotli (compression library) |
| Affected versions | 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 |
| Severity | 9.2 Critical (CVSS 4.0, Google) |
| Who can attack | A remote attacker with no login, if the app unpacks Brotli data the attacker supplies |
| Exploited | No attacks reported as of 23 October 2026 |
| CVE published | 22 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.brotliDecompresszlib.brotliDecompressSynczlib.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:
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:
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
- 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
nodebinary, or in the system Brotli library for Debian, Ubuntu and Alpinenodejspackages. On Alpine, also updatebrotli-libs. Debian and Ubuntu have no fixedlibbrotli1yet: move those servers to the official binaries or anodeDocker image. - Rebuild your Docker images from a fixed base image, such as
node:22.23.4in your Dockerfile'sFROMline. Then redeploy every container: a running container keeps its oldnodeprogram. - Move servers off 20.x and 25.x: Node.js shipped no fix for them.
- 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.
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
Sources
- CVE-2026-111497 record CVE Program
- Wednesday, October 21, 2026 Security Releases Node.js project
- Brotli v1.2.1 release (also v1.1.1, v1.0.10) Google (google/brotli on GitHub)
- CVE-2026-111497 in the Debian security tracker Debian Security Team
- CVE-2026-111497 Canonical (Ubuntu Security)
- 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.