Threat level Guarded
Submit a tip

Major threats, straight to your inbox

Only the threats that matter: actively exploited flaws, big breaches and attacks that need action. No spam, unsubscribe any time.

Node2Shell CVE-2026-111497 Exploited: Brotli Decoder Flaw Hits Node.js

CISA says attackers are exploiting Node2Shell (CVE-2026-111497), an out-of-bounds write in the Brotli decoder that Imperva turned into remote code execution in Node.js through fetch() responses and Express 5 request bodies. Node.js 22.23.4, 24.22.1 and 26.12.1 fix it.

Node2Shell CVE-2026-111497 Exploited: Brotli Decoder Flaw Hits Node.js

Threat card

Status
Actively exploited
Threat type
Vulnerabilities
Disclosed
Oct 21, 2026
Affected
Node.js 22.x before 22.23.4, 24.x before 24.22.1 and 26.x before 26.12.1, including Express 5.0.0 to 5.3.0 and body-parser 2.0.0 to 2.3.0 apps that decode Brotli bodies; other HTTP servers and clients using vulnerable Brotli code

The short version

  • Node2Shell (CVE-2026-111497) is an out-of-bounds write in the Brotli decoder that can lead to remote code execution.
  • CISA confirmed in-the-wild exploitation, added the flaw to KEV on 27 October and set a 10 November federal deadline.
  • Imperva reached code execution in Node.js through fetch() responses and Express 5 or body-parser 2 request bodies.
  • Node.js 22.23.4, 24.22.1 and 26.12.1 fix the flaw, and Microsoft shipped an emergency .NET update.

Node2Shell, tracked as CVE-2026-111497, is an out-of-bounds write in the Brotli decompression code bundled with Node.js and other HTTP stacks, and CISA confirmed on 27 October 2026 that attackers are exploiting it. A crafted Brotli stream can crash a process, leak memory or, as Imperva demonstrated, run attacker code inside a Node.js server. Node.js 22.23.4, 24.22.1 and 26.12.1 fix it, and Microsoft shipped an emergency .NET update. Any team running Node.js services or Express 5 apps that accept Brotli bodies should patch, restart and rebuild container images now.

What happened

CVE-2026-111497 is a memory corruption bug in the Brotli decoder that unauthenticated attackers can trigger with compressed data. Node.js disclosed it on 21 October, Imperva published a remote code execution proof of concept the next day, and CISA added it to the Known Exploited Vulnerabilities catalog on 27 October with a federal patch deadline of 10 November.

The flaw also circulates under the names Broccoli2Shell and HTTP2Shell. BleepingComputer reports that it was first found in Node.js but also affects HTTP servers and clients that use vulnerable Brotli implementations, and that Microsoft released emergency .NET patches because the bug could be used to escalate privileges on vulnerable .NET versions.

Timeline

Date Event
21 October 2026 Node.js discloses CVE-2026-111497 and ships fixed releases; reported by Matteo Collina, fixed by Antoine du Hamel
22 October 2026 Imperva publishes Node2Shell research with a code execution demonstration
25 October 2026 Microsoft releases emergency .NET updates for the Brotli flaw
27 October 2026 CISA confirms exploitation and adds the CVE to KEV
10 November 2026 CISA BOD 26-04 remediation deadline for federal agencies

How the attack works

Root cause

According to Imperva’s Node2Shell analysis, the decoder reaches a block transition that a valid Brotli stream can never produce. Instead of failing, the vulnerable code treats it as a need for more input and keeps running with an invalid internal state, which can write past the intended buffer. The upstream Google Brotli fix makes the decoder return a format error for that transition.

Attack vectors

Imperva identified two reachable paths in Node.js. The first is a Brotli-compressed HTTP response that the application consumes with the built-in fetch(), so a malicious or compromised upstream server can attack the client. The second is an incoming request body: Express 5 and body-parser 2 decompress Brotli bodies when parsers such as raw() or json() are configured, so a remote client can attack the server with a header like Content-Encoding: br.

A bare Node.js HTTP server does not decode incoming Brotli bodies on its own, which narrows exposure to apps that opt in through middleware or that fetch untrusted content.

Impact

The primitive is an out-of-bounds write. Imperva’s proof of concept ran attacker-supplied code in the Node.js process and created a marker file, though success took several attempts in its setup. In practice the result ranges from denial of service to code execution with the privileges of the service.

MITRE ATT&CK mapping

Tactic Technique (ID) How it was used here
Initial Access Exploit Public-Facing Application (T1190) Crafted Brotli request bodies sent to Express 5 apps
Execution Exploitation for Client Execution (T1203) Malicious Brotli responses consumed by fetch()
Privilege Escalation Exploitation for Privilege Escalation (T1068) Privilege escalation on vulnerable .NET versions, per BleepingComputer
Impact Endpoint Denial of Service (T1499) Process crashes from malformed streams

Who is behind it

Not yet attributed. CISA confirmed exploitation but has not named an actor or published campaign details. No public indicators tie the activity to a known group.

Affected products and versions

Product Affected Fixed CVE CVSS
Node.js 22.x Before 22.23.4 22.23.4 CVE-2026-111497 Not disclosed
Node.js 24.x Before 24.22.1 (24.22.0 tested) 24.22.1 CVE-2026-111497 Not disclosed
Node.js 26.x Before 26.12.1 26.12.1 CVE-2026-111497 Not disclosed
Express / body-parser 5.0.0 to 5.3.0 / 2.0.0 to 2.3.0 (reachable paths) Fixed by the Node.js runtime update CVE-2026-111497 Not disclosed
.NET Vulnerable versions per Microsoft Emergency .NET update CVE-2026-111497 Not disclosed

Node.js rates the issue high severity, while CISA and press coverage describe it as critical. The NVD entry is the place to watch for a final score.

Indicators of compromise

No IOCs have been published by CISA, Node.js or Imperva. Expect detail in later vendor or CISA advisories. Until then, use behavioural signs: unexpected process exits during decompression, Brotli decoder errors in application logs, and request bodies with Content-Encoding: br arriving at endpoints that normally receive uncompressed JSON. Imperva notes that crashes and decoder errors help prioritise investigation but are not proof of exploitation alone.

Detection and hunting

At the edge, log the Content-Encoding header on inbound requests and alert on Brotli bodies sent to API routes. Imperva has added dedicated WAF rules for CVE-2026-111497, and other WAF vendors may follow. In application telemetry, look for Node.js workers restarting with segmentation faults or aborts close to POST requests.

On hosts, a Node.js process spawning a shell, curl, wget or package managers is a strong sign of post-exploitation. For outbound risk, review which services call fetch() against third-party URLs and accept compressed responses. Recent Threatspedia coverage of PHP2Shell attacks on Check Point gateways shows how quickly these parser bugs move into real intrusions.

Mitigation and response

  1. Upgrade Node.js to 22.23.4, 24.22.1, 26.12.1 or later, and move unsupported release lines to a supported one.
  2. Apply Microsoft’s emergency .NET update and check other runtimes and libraries that bundle Brotli.
  3. Restart patched processes and rebuild and redeploy every container image that ships its own Node.js binary.
  4. Where patching is delayed, block Brotli-compressed request bodies at the proxy or firewall, or disable Brotli decoding in middleware.
  5. Inventory where untrusted Brotli data reaches your runtimes, including outbound fetch() calls.
  6. Hunt for crashes, decoder errors and unusual child processes on internet-facing Node.js services since 21 October.

Analyst take

Node2Shell is a reminder that compression code sits in the hot path of almost every web stack and gets little scrutiny. A single decoder bug reached Node.js, .NET and other HTTP implementations at once, and exploitation followed within a week of disclosure. That is the same speed defenders saw with other parser bugs this year.

The hardest part is not the patch but finding every copy of the runtime. Node.js binaries live inside container images, desktop apps and build agents, and many of them are never updated by the host package manager. Teams that cannot list where Node.js runs should treat this as the trigger to build that inventory.

What to do now

0 of 5 done

Questions readers ask

What is Node2Shell?

Node2Shell is the name for CVE-2026-111497, an out-of-bounds write in the Brotli decoder that a crafted compressed stream can use to crash a process or run code.

Which Node.js versions fix CVE-2026-111497?

Node.js 22.23.4, 24.22.1 and 26.12.1 and later releases in each line contain the fix.

Is Node2Shell being exploited?

Yes. CISA confirmed active exploitation and added CVE-2026-111497 to its Known Exploited Vulnerabilities catalog on 27 October 2026.

Sources

  1. Imperva: Node2Shell, from Brotli data to remote code executionimperva.com
  2. Node.js: October 2026 security releasesnodejs.org
  3. CISA: CISA adds two known exploited vulnerabilities to catalogcisa.gov
  4. NVD: CVE-2026-111497nvd.nist.gov
  5. BleepingComputer: CISA warns of hackers now exploiting critical Node2Shell flawbleepingcomputer.com
Share this story
Get the next major threat first

One short email when something serious breaks.

Threatspedia Desk

Threatspedia covers major cyber threats only, verified against primary sources. Read our editorial policy, or report a correction.

Threat alerts

Be first to know when a major threat breaks.

One short email when something serious happens, plus a weekly roundup. Free, no noise.