Updated 29 October 2026 (Cyprus time, UTC+2): On 28 October at 19:47 Cyprus time, NVD completed its analysis of CVE-2026-111497 (status "Analyzed") and published its own CVSS 3.1 score: 9.8, which NVD labels Critical (NVD). Our earlier text said NVD had not yet scored the flaw; we corrected the summary, technical details, timeline, sources and update list. We also updated the support status of the 26.x line, which Node.js moved to Long Term Support on 28 October, and of the 24.x line, now in maintenance. Nothing else has changed: Node.js has not changed its own rating, Google's CVSS 4.0 score is still 9.2, and the CISA KEV entry (added 27 October, due 10 November, ransomware use "Unknown") and the fixed versions are the same.
Earlier update, 28 October 2026 (08:30 Cyprus time, UTC+2): On 27 October, CISA added CVE-2026-111497 to its Known Exploited Vulnerabilities (KEV) catalog "based on evidence of active exploitation," and set 10 November 2026 as the remediation due date for US federal civilian agencies (CISA alert, 27 October 2026). CISA lists the entry under Google Brotli, the library inside Node.js, and marks known ransomware use as "Unknown". CISA has not said who is exploiting the flaw or against which targets. The fix has not changed: Node.js 22.23.4, 24.22.1 and 26.12.1, or Brotli 1.0.10, 1.1.1 and 1.2.1. We updated the summary, exploitation status, timeline, indicators, guidance and sources, and replaced our earlier exploitation and KEV status from 23 October, which is now out of date.
On 21 October 2026, the Node.js project released 22.23.4, 24.22.1 and 26.12.1 for all three supported release lines. The most serious fix is CVE-2026-111497, an out-of-bounds write in the Brotli decoder that Node.js bundles. Node.js says the flaw "permits remote code execution" and rates it High. The CVE record comes from Google, the CNA for the Brotli library. Google gives it a CVSS 4.0 score of 9.2 (labelled Critical on NVD). On 28 October NVD finished its analysis (status "Analyzed") and published its own CVSS 3.1 score of 9.8, which NVD labels Critical (vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Imperva's Red Team calls its analysis of the flaw "Node2Shell".
A Node.js service is exposed only if it, or a library it uses, decompresses Brotli data that an attacker controls. Imperva tested two such routes: Node.js's built-in fetch() reading a Brotli-compressed response, and Express 5 or body-parser 2 decoding a Brotli-compressed request body. The risk picture changed on 27 October: CISA now lists CVE-2026-111497 in KEV, which means CISA has evidence of exploitation in the wild. Other facts still put the risk in context. Node.js rates the flaw High, not Critical. Imperva says code execution "took multiple attempts" in its own lab. No victim has been named, and fixed versions have been available since 21 October. Node.js 20.x and older are end of life and will not get a fix.
Technical Information
What Node.js says (Node.js security release, 21 October 2026):
- Node.js titles the flaw "Node.js Brotli decoder out-of-bounds write permits remote code execution (CVE-2026-111497)" and says it affects the 26.x, 24.x and 22.x lines.
- Node.js credits "OpenAI Codex Security - Khai Tran and Sylvie Mayer" with the report, and Node.js maintainers Matteo Collina and Antoine du Hamel with the fix.
- "End-of-Life versions are always affected when a security release occurs."
- The release notes show the fix as a cherry-pick of an upstream Brotli commit, plus a new decoder error code (
BROTLI_DECODER_ERROR_FORMAT_BLOCK_SWITCH) that patched Node.js returns when it rejects an invalid stream (Node.js 24.22.1 release notes).
When we re-checked it on 29 October, the Node.js security release page still showed "Last Updated Oct 21, 2026" and did not mention exploitation.
What the CVE record says. Google's record on cve.org describes a buffer overflow in the Brotli decoder in Google Brotli 1.0.3 through 1.2.0 that "allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream." Its CVSS 4.0 vector requires no privileges or user interaction, but it marks attack requirements as present (AT:P), which means the attack depends on conditions in the target's setup. CVSS 3.1 has no attack-requirements metric, so NVD's 9.8 vector does not capture that condition. The weaknesses listed are CWE-787 (out-of-bounds write) and CWE-252 (unchecked return value). Google released Brotli 1.0.10, 1.1.1 and 1.2.1 with the fix (Brotli 1.2.1 release).
Beyond Node.js. CISA's KEV entry notes that the flaw "affects an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products." Two examples from the projects' own advisories:
- .NET. Microsoft's advisory for CVE-2026-111497 covers the Brotli decoder in .NET and lists fixed runtimes 8.0.33, 9.0.22 and 10.0.14 (Microsoft .NET advisory, dotnet/announcements #494).
- Python. The GitHub-reviewed advisory GHSA-9v8h-qqgm-4m35 lists the PyPI
brotlipackage as fixed in 1.2.1 andbrotlicffiin 1.2.1.0 (GitHub advisory GHSA-9v8h-qqgm-4m35).
Other software that bundles or links an affected Brotli version, including Linux distribution packages, may need its own update.
How the decoder is reached. Node.js does not decode Brotli on its own. Vercel puts it this way: "Your application is exposed when its code, or a library it uses, decompresses Brotli data an attacker controls, whether in a request body or in a response it fetches" (Vercel bulletin). Imperva tested two routes (Imperva, 22 October 2026):
- Responses a service fetches. Node.js's built-in
fetch()consuming a Brotli-compressed response from another server. - Request bodies a service receives. Express 5.0.0–5.3.0 and body-parser 2.0.0–2.3.0, using the
raw()andjson()parsers. Imperva notes that "the vulnerable code is in Node.js: these middleware versions identify paths that can invoke it," and that "a bare Node.js HTTP server does not decode incoming Brotli bodies simply by receiving them."
How far exploitation has been shown. Imperva says its proof of concept ran code supplied in Brotli data inside test applications on the official Node.js 24.22.0 Linux arm64 image, and that 24.22.1 rejected the same inputs. It adds that "execution took multiple attempts in our setup" and that it "did not test every Node.js build or application." On 22 October, The Hacker News reported that a separate public proof of concept "reached code execution only against a deliberately weakened test build." Since then, threat intelligence firm ELLIO has said it reproduced code execution on official, unmodified Node.js 24.22.0 builds on x86-64 in its own lab (ELLIO, Node2Shell analysis). We do not link proof-of-concept code.
Exploitation status. CISA added CVE-2026-111497 to the KEV catalog on 27 October 2026 with a due date of 10 November 2026 (CISA KEV catalog). CISA adds a flaw to KEV when it has evidence of active exploitation, but it does not publish that evidence. The entry marks known ransomware campaign use as "Unknown" and asks agencies to apply the vendor's mitigations or stop using the product if mitigations are not available. CISA's assessment attached to the NVD record now lists exploitation as "active" (it said "none" on 22 October), with automatable "no" and technical impact "total" (NVD). Separately, ELLIO said in an update dated 26 October that its sensors recorded exploit traffic for the flaw in the wild, aimed at Node.js 24.22.0 on x86-64. ELLIO says that in its own testing the observed attack chain crashed the process rather than reaching code execution, and it describes the attempt as likely "first-generation." These are ELLIO's own observations; CISA has not said what evidence it relied on, and no victim has been named. When we re-checked on 29 October, Node.js had not published any statement on exploitation.
Other fixes in the same release. The release fixes nine more CVEs and updates bundled dependencies (c-ares, OpenSSL, SQLite, undici and the root certificate store). The ones most relevant to suppliers that make outbound TLS connections:
| CVE | Issue (Node.js wording, shortened) | Node.js severity | Lines affected |
|---|---|---|---|
| CVE-2026-106069 | TLS certificate hostname bypass when the host loosely resolves to an IP address | High | 26.x, 24.x, 22.x |
| CVE-2026-105483 | TLS certificate hostname bypass when the IP is written in fullwidth digits | High | 26.x, 24.x |
| CVE-2026-105482 | dns.resolve truncates names containing a NUL character |
High | 26.x, 24.x, 22.x |
| CVE-2026-106072 | Non-canonical IPv4 hostnames let DNS names in certificates authenticate IP endpoints | Medium | 26.x, 24.x, 22.x |
The same release also blocks the compromised eMudhra intermediate CA keys, which we covered in our eMudhra intermediate CA key compromise advisory.
Timeline (times in Cyprus time, UTC+3 until 25 October and UTC+2 after, where the source gives one):
- 21 October 2026: Node.js publishes the security release and ships 22.23.4, 24.22.1 and 26.12.1. Vercel says it deployed WAF rules for inbound traffic the same day.
- 21 October, 22:27: Google publishes Brotli 1.0.10, 1.1.1 and 1.2.1 on GitHub, each listing CVE-2026-111497 under "SECURITY".
- 22 October, 16:35: Google publishes the CVE record (CVSS 4.0: 9.2).
- 22 October, 17:15–17:17: The record reaches NVD ("Awaiting Analysis"), with CISA's assessment of no known exploitation at that time.
- 22 October: Imperva publishes "Node2Shell: From Brotli Data to Remote Code Execution". France's CERT-FR publishes CERTFR-2026-AVI-1367, and Hong Kong's GovCERT.HK publishes High Threat Security Alert A26-10-37. GovCERT.HK says "reports indicate that proof-of-concept (PoC) exploit code is available for the vulnerabilities."
- 25 October: Microsoft publishes its .NET advisory for CVE-2026-111497.
- 26 October, 17:08 (15:08 UTC): ELLIO says its sensors recorded exploit traffic for the flaw in the wild.
- 27 October, 21:00 (19:00 UTC): CISA releases KEV catalog version 2026.10.27, adding CVE-2026-111497 (date added 27 October, due 10 November), and posts its alert the same day.
- 28 October, 19:47 (17:47 UTC): NVD completes its initial analysis (status "Analyzed") and publishes its own CVSS 3.1 score: 9.8, which NVD labels Critical. Google's CVSS 4.0 score of 9.2 stays on the record alongside it.
Affected Product Versions
Per the Node.js security release and release notes (21 October 2026) and the Node.js release schedule.
| Node.js line | Support status | Affected | Fixed version |
|---|---|---|---|
| 26.x | LTS (since 28 October 2026) | Releases before 26.12.1 | 26.12.1 |
| 24.x | LTS (maintenance) | Releases before 24.22.1 | 24.22.1 |
| 22.x | LTS (maintenance) | Releases before 22.23.4 | 22.23.4 |
| 25.x and 23.x | End of life (1 June 2026 and 1 June 2025) | Affected, per Node.js's end-of-life statement | No fix. Move to a supported line |
| 20.x and older | End of life (20.x on 30 April 2026) | Affected, per Node.js's end-of-life statement | No fix. Move to a supported line |
Per Google's CVE record, the underlying library is affected in Google Brotli 1.0.3 before 1.0.10, 1.1.0 before 1.1.1, and 1.2.0 before 1.2.1. The fixed library versions are 1.0.10, 1.1.1 and 1.2.1. For .NET and the Python packages, see the fixed versions under "Beyond Node.js" above.
Notes (Rescana guidance):
- Bundled runtimes. Containers, serverless images, desktop apps and CLI tools often ship their own Node.js binary. Imperva warns that "a package inventory can miss an older runtime bundled in a container."
- Updating npm packages is not enough. The flaw is in the Node.js runtime, so updating Express, body-parser or other npm packages does not fix it. Only a fixed Node.js release does.
- Exposure is not compromise. Running an affected version only matters where the service decompresses untrusted Brotli data. A KEV listing means the flaw is being exploited somewhere, not that a given supplier has been hit.
Workaround and Mitigation
1. Upgrade Node.js now. With the flaw in KEV, treat CISA's 10 November date as the latest acceptable date, not the plan (Rescana guidance). Move every runtime to 22.23.4, 24.22.1, 26.12.1 or later. Imperva advises including "container images and other artifacts that bundle a Node binary," and checking "the Node.js version inside each deployed image or host." Vercel's advice covers "external backends, self-hosted Next.js, container images you build yourself, CI runners and local development."
2. Move off end-of-life lines. Node.js 20.x and older, and 23.x and 25.x, receive no fix. Vercel tells customers that "Node.js 20 reached end of life and will not receive this fix," and asks projects still on 20.x to switch to 22.x or 24.x and redeploy.
3. Patch other copies of Brotli. Update system Brotli libraries to 1.0.10, 1.1.1 or 1.2.1 (or your distribution's fixed package), .NET runtimes to the fixed versions in Microsoft's advisory, and the Python brotli and brotlicffi packages. Rebuild and redeploy images that bundle any of them.
4. Until you can upgrade, reduce untrusted Brotli input. Imperva suggests that, "where practical, temporarily limit untrusted Brotli traffic on affected paths while updates roll out," and test against normal traffic. For services that do not need compressed request bodies, body-parser documents an inflate: false option that "rejects encoded requests before any decompression stream is created" (body-parser advisory GHSA-27r3-jxmh-p828). This only covers inbound bodies. Vercel notes that "only the runtime patch covers fetched responses."
5. Treat WAF rules as a stopgap. Imperva and Vercel both say they have added WAF rules. Vercel says its rules do not cover "responses your functions fetch from other servers" and that the WAF "does not replace patching."
6. Look back, not just forward (Rescana guidance). Because the flaw is now known to be exploited, review internet-facing Node.js services that accepted Brotli-compressed request bodies before they were patched. Imperva's investigation hints are under Indicators of Compromise below.
Express and body-parser. Neither project has published an advisory for CVE-2026-111497. Express's security advisories list has no new entry, and its latest release (5.3.0, 9 October) predates the Node.js fix. On 22 October, body-parser did publish a separate advisory, GHSA-27r3-jxmh-p828 (CVE-2026-111181, which body-parser rates High at CVSS 3.1 7.5). It covers a denial of service from trailing bytes after a compressed request body and is fixed in body-parser 2.4.0 and 1.20.9. That advisory is not about the Brotli decoder flaw, but it affects the same compressed-body path, so it is worth applying at the same time.
Indicators of Compromise
Node.js, Google, CISA, Imperva, Vercel, CERT-FR and GovCERT.HK have published no indicators of compromise for CVE-2026-111497. ELLIO has published two indicators from the exploit traffic its sensors recorded on 26 October (ELLIO). They are shown here defanged and attributed to ELLIO; we have not verified them independently:
| Type | Value (per ELLIO) | Note |
|---|---|---|
| Source IP | 94.154.43[.]7 | ELLIO rates it malicious with high confidence |
| SHA-256 of the Brotli-compressed request body (23,069,983 bytes) | 7fcbdaaecd4419e2930927844f3b772668204737a4e7602a2290c991c93c5c4b | Single request seen by ELLIO's sensors |
One source address and one payload hash are a narrow basis for detection, and a missing match does not show a service was not targeted. Imperva says "unexpected process exits during decompression and decoder errors may help prioritize investigation," but "neither is a reliable stand-alone sign of exploitation." It suggests correlating them with the deployed runtime, application logs and the source of the compressed data. None of the primary sources maps the flaw to MITRE ATT&CK, and we have not done so either.
What we will update
We will update this post if Node.js or Google reports exploitation or changes its fix guidance, if CISA or a national CERT publishes more detail on the exploitation, if CISA changes the ransomware field on the KEV entry, or if Express or body-parser publish guidance on the Brotli flaw.
Sources
- Node.js: "Wednesday, October 21, 2026 Security Releases": https://nodejs.org/en/blog/vulnerability/october-2026-security-releases; release notes for 22.23.4, 24.22.1 and 26.12.1; release schedule and end-of-life dates (Node.js Release working group): https://github.com/nodejs/Release
- Google (CNA) and the Brotli project: CVE-2026-111497 record: https://www.cve.org/CVERecord?id=CVE-2026-111497; Brotli 1.2.1 release: https://github.com/google/brotli/releases/tag/v1.2.1
- CISA and NVD: CISA, "CISA Adds Two Known Exploited Vulnerabilities to Catalog" (27 October 2026): https://www.cisa.gov/news-events/alerts/2026/10/27/cisa-adds-two-known-exploited-vulnerabilities-catalog; CISA, Known Exploited Vulnerabilities catalog (checked 29 October 2026, 16:18 Cyprus time, UTC+2; catalog version 2026.10.28; CVE-2026-111497 listed, date added 27 October, due 10 November, ransomware use "Unknown"): https://www.cisa.gov/known-exploited-vulnerabilities-catalog; NVD, CVE-2026-111497 (checked 29 October 2026, 16:18 Cyprus time, UTC+2; status "Analyzed"; NVD Primary CVSS 3.1 9.8 Critical, last modified 28 October 19:47 Cyprus time; Google CVSS 4.0 9.2 and CISA assessment attached): https://nvd.nist.gov/vuln/detail/CVE-2026-111497
-
Other affected projects and the Express project: Microsoft, ".NET Brotli Decoder Out-of-bounds Write Vulnerability" (dotnet/announcements #494, 25 October 2026): https://github.com/dotnet/announcements/issues/494; GitHub advisory GHSA-9v8h-qqgm-4m35 (PyPI
brotliandbrotlicffi): https://github.com/advisories/GHSA-9v8h-qqgm-4m35; body-parser advisory GHSA-27r3-jxmh-p828 (22 October 2026): https://github.com/expressjs/body-parser/security/advisories/GHSA-27r3-jxmh-p828; Express security advisories: https://github.com/expressjs/express/security/advisories - National CERTs: CERT-FR, CERTFR-2026-AVI-1367 (22 October 2026, French): https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-1367/; GovCERT.HK, security alert A26-10-37 (22 October 2026): https://www.govcert.gov.hk/en/alerts_detail.php?id=2126
- Security vendors and press: Imperva, Ron Masas, "Node2Shell: From Brotli Data to Remote Code Execution" (22 October 2026): https://www.imperva.com/blog/node2shell-from-brotli-data-to-remote-code-execution/; ELLIO, "Node2Shell: remote code execution on stock Node.js builds (CVE-2026-111497)" (update of 26 October 2026): https://ellio.tech/en/blog/node2shell-cve-2026-111497-rce-on-stock-nodejs-builds/; Vercel, "Node.js security advisory: Brotli decoder RCE (CVE-2026-111497)": https://vercel.com/kb/bulletin/node-js-security-advisory; The Hacker News, "Node.js Brotli Decoder Bug Could Allow Remote Code Execution in All Supported Versions" (22 October 2026): https://thehackernews.com/2026/10/nodejs-brotli-decoder-bug-could-allow.html
Node.js runs the APIs, web backends and integration services of a large share of SaaS suppliers, often inside container images that are rebuilt less often than application code. Now that CISA lists this flaw as exploited, whether a supplier can tell you quickly which Node.js runtime it runs, and where it decompresses data from outside, is a good test of how well it knows its own stack.
Forward this to your TPRM owner: Send your key SaaS suppliers a short, friendly check before 10 November (Rescana guidance):
- Are your production services, container images and build agents on Node.js 22.23.4, 24.22.1, 26.12.1 or later? If not, when do you plan to upgrade?
- Have you also updated other copies of Brotli you run, such as system libraries, .NET runtimes or Python packages?
- Do you still run Node.js 20.x or another end-of-life line anywhere, including bundled runtimes? What is your plan to move off it?
- Do any of your services decompress Brotli data from untrusted sources, such as compressed request bodies (for example through Express 5 or body-parser 2) or responses fetched from third-party servers? Have you reviewed those services for signs of exploitation from before they were patched?
Want a fast, evidence-based view of how your suppliers handle runtime fixes like this one?



