Node2Shell: a Node.js flaw can run code from compressed data. Update Node
Node.js fixed a Brotli decoder bug on 21 Oct 2026 that can lead to remote code execution in apps that decompress Brotli data. No attacks in the wild were reported when we published; CISA now lists it as exploited (update of 28 Oct). Here is who is affected and what to check.
Updated 4 Nov 2026: see what changedHow urgent
Act now
Who is affected
Apps running Node.js 22.x, 24.x or 26.x below 22.23.4, 24.22.1 or 26.12.1 that decompress Brotli data from outside, for example responses from other services or request bodies handled by Express or body-parser
What to do
Run node -v, update to 22.23.4, 24.22.1 or 26.12.1 (or later) and move off Node 20, which reports say gets no fix
Published 25 Oct 2026 · Sources last checked 4 Nov 2026No. 12 / 87
Updates, follow-ups and corrections
- Update · 4 Nov 2026. The same 21 October release fixed nine more flaws, and another security release is announced for 11 November. Besides the Brotli bug, the release page lists three more high-severity flaws (CVE-2026-105482 in DNS lookups, and CVE-2026-105483 and CVE-2026-106069 in how Node checks which IP address a certificate was issued for), three medium and three low ones, and says end-of-life versions are affected too. The page does not report exploitation of these nine; CISA's entry covers only the Brotli bug. Node.js's index also lists a "November 11, 2026 Security Releases" entry (listed on 3 Nov, title only, no details yet). The action stays the same: update to 22.23.4, 24.22.1 or 26.12.1 or later, redeploy, and check again on 11 November. We read the release page and the index, not the CVE records.
- Update · 28 Oct 2026. CISA added CVE-2026-111497 (listed as Google Brotli) to its Known Exploited Vulnerabilities catalog on 27 Oct 2026, which means it counts the flaw as exploited in attacks. When we published we said no attacks were reported; that is no longer true. CISA's entry names the Brotli library, not Node.js, lists Brotli 1.2.1 as the fix and sets a deadline of 10 Nov for US federal agencies. We have not seen details of who is attacking or how. Update Node.js to 22.23.4, 24.22.1 or 26.12.1, and any other software that bundles Brotli, and treat this as urgent. We raised the severity of this story to "act".
We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.
What happened
On 21 October 2026 the Node.js project published security releases. One of them fixes CVE-2026-111497, a bug in the Brotli decoder built into Node.js. Brotli is a way of compressing data, and the decoder is the code that unpacks it. The Node.js advisory (rated High) says that specially crafted Brotli data can write past an eight-byte internal buffer, which can lead to a crash, to leaking memory from the process, or to remote code executionRCE (remote code execution) A flaw that lets an attacker run their own code on your server or device from a distance. Tap again to open the glossary. The attacker needs to get Brotli data into something your app decompresses with Node's built-in node:zlib.
The advisory credits OpenAI Codex Security (Khai Tran and Sylvie Mayer) with reporting the bug, and Matteo Collina and Antoine du Hamel with the fix. The security firm Imperva named it Node2Shell.
What we could and could not confirm
Imperva's Red Team published its own analysis on 22 October. It says it got code running on the official Node.js 24.22.0 Linux arm64 image using Brotli data carried in a request or response body. It took several attempts, and Imperva has not published the code. Version 24.22.1 rejected the same inputs. The sources we read report no attacks in the wild. Imperva also says that a crash or a decoder error is not, on its own, a reliable sign that someone attacked you.
Severity is described differently depending on who you ask. Node.js rates it High. Press reports say Google, which assigned the CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary, scores it 9.2 (Critical) on CVSSCVSS score A number from 0 to 10 that rates how serious a flaw is in general. From 9.0 up it is called Critical. Tap again to open the glossary v4.0 and that Red Hat scored it 8.1. We use Node.js's own rating. The same press reports say the fix for the underlying bug reached Brotli's source code in February but no release followed until now. We could not confirm that timeline in a primary source, and we could not open OpenAI's own post on X.
Who is affected
Apps running Node.js 22.x, 24.x or 26.x that have not yet moved to 22.23.4, 24.22.1 or 26.12.1, and that decompress Brotli data coming from outside. Imperva found these cases:
- Node's built-in
fetch()decoding a compressed response from another server. - Express 5.0.0 to 5.3.0 and body-parser 2.0.0 to 2.3.0, when Brotli-capable parsers such as
raw()andjson()are set up. Imperva tested only specific pinned configurations. - A bare Node.js HTTP server does not decode incoming Brotli bodies just by receiving them.
Press reports say Node 20 gets no fix, that Bun is also affected, and that other software that bundles Brotli, such as Python packages and Envoy, is being patched separately. Check your own vendors.
What to do
- Run
node -von your servers, in your containers and in your hosting settings. Update to 22.23.4, 24.22.1 or 26.12.1, or later, in your line. If you are on Node 20, plan the move to a supported line. - Rebuild your container images and redeploy, so the new Node version is the one that runs.
- Find where your app accepts Brotli data: calls to other services with
fetch(), Express or body-parser with Brotli parsers, and uploads or API bodies decompressed withnode:zlib. - Update your dependencies and the tools that bundle Brotli, and ask your host or vendor if they run Node for you.
- Do not treat a crash as proof of an attack, and do not treat the lack of one as proof you are safe. Update first.
If you build with AI tools
Our advice, not from the advisory: apps written with an AI assistant often rely on Express defaults and on calls to third-party services, so you may not know which of the cases above apply to you. Pin the Node version in your Dockerfile or hosting settings, turn on automatic dependency updates, and ask your assistant to list where your code decompresses data or fetches from other services. Until you have updated, limiting which services your app calls and which clients can send it compressed data reduces exposure, but it is not a fix.
Watch the short video
The video loads from YouTube (privacy-enhanced mode) only when you press play.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
- Node.js security release, 21 Oct 2026 (CVE-2026-111497, rated High) (opens in a new tab)
- Imperva Red Team, Node2Shell analysis, 22 Oct 2026 (opens in a new tab)
- Press coverage used only for the timeline and scores we could not confirm in a primary source: SOC Prime, Cyber Kendra and WebProNews, Oct 2026 (opens in a new tab)
- CISA: Known Exploited Vulnerabilities catalog, entry CVE-2026-111497 (Google Brotli), added 27 Oct 2026, due date 10 Nov 2026 (opens in a new tab)
- Node.js: security releases index, entry "Wednesday, November 11, 2026 Security Releases" (listed 3 Nov 2026, title only, read directly) (opens in a new tab)
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.