Skip to content

Node2Shell (CVE-2026-111497): Actively Exploited Remote Code Execution Vulnerability in Node.js Brotli Decoder

Ciphertronix Cyber Security Advisory CTX-ADV-2026-1118-C: Node2Shell, CVE-2026-111497, an actively exploited remote code execution vulnerability in the Node.js Brotli decoder, with a shield and padlock in front of a laptop showing the Node.js logo
Advisory ref.
CTX-ADV-2026-1118-C
Date of issue
21 October 2026
Severity
CRITICAL (Actively Exploited)
Classification
TLP:CLEAR
Audience
Banks, DFIs, microfinance banks, PSOs/PSPs and fintech partners
CVE
CVE-2026-111497

1. Executive summary

Ciphertronix Security Operations is issuing this advisory about Node2Shell (CVE-2026-111497). It is also called HTTP2Shell or Broccoli2Shell, and is an out-of-bounds write in the Brotli decoder that ships inside Node.js. An attacker who can supply malformed Brotli-compressed data can corrupt process memory, which can lead to a crash, disclosure of process memory, or remote code execution (RCE).

CISA added the CVE to the Known Exploited Vulnerabilities catalogue on 27 October 2026. Akamai telemetry shows that 61% of networks are running affected Node.js versions. Node.js is widely used in banks for mobile banking back ends, API gateways, customer portals and integration services, so Ciphertronix recommends that every institution identifies and patches affected runtimes immediately.

2. Vulnerability details

ItemDetail
CVE IDCVE-2026-111497
NameNode2Shell (also HTTP2Shell, Broccoli2Shell)
ComponentGoogle Brotli decompression library, bundled inside Node.js and Bun
SeverityCritical. Google, as the CNA, scored it 9.2 (Critical) under CVSS 4.0. Node.js rates it High.
Discovered byKhai Tran and Sylvie Mayer of OpenAI Codex Security found and reported the bug to Node.js.
Attack vectorNetwork. The attack works against applications that decompress Brotli data from untrusted sources.
Exploitation statusA public proof of concept exists, and code execution has been demonstrated on the official Node.js 24.22.0 arm64 image. CISA confirmed exploitation in the wild.

3. Which applications are exposed

Node2Shell only hits Node.js applications that decompress Brotli data from untrusted sources, such as Express 5 with body-parser 2 or fetch() calls to third-party servers. Exposure paths include:

  • body-parser / Express 5 with express.json(): exposed by default, since body-parser 2.x decodes br bodies.
  • Server-side fetch(): decompresses Brotli responses when Content-Encoding includes br, even with Accept-Encoding: identity. Services calling attacker-influenced URLs (for example webhooks) are at risk.
  • Direct node:zlib: createBrotliDecompress() is exposed when it processes attacker-controlled data.
  • Other frameworks: Koa (via co-body), plus @koa/bodyparser, koa-body, Egg, and Strapi; Fastify with @fastify/compress.

Express 4 and body-parser 1.x do not decode Brotli request bodies. Static websites that use Node only at build time are not affected in operation.

4. Affected and fixed versions

PlatformAffectedRecommended fixed version
Node.js 26.xBefore 26.12.126.12.1
Node.js 24.xBefore 24.22.124.22.1
Node.js 22.xBefore 22.23.422.23.4
Node.js 25.x and 20.xAffected; end of life, no fixUpgrade to a supported line
BunBefore 1.4.41.4.4
Google Brotli library1.0.3 to 1.0.9, 1.1.0, 1.2.01.0.10, 1.1.1, 1.2.1
Python brotli / brotlicffiBefore 1.2.1 / before 1.2.1.01.2.1 / 1.2.1.0
.NET runtimeEarlier builds8.0.33, 9.0.22, 10.0.14

Note. .NET Framework is not affected. For .NET, Brotli decompression is off by default, so only apps that enable it are exposed. Distribution packages may be unpatched even when the Node.js version number looks current.

5. Potential impact

  • Remote code execution on API servers, mobile banking back ends and integration services
  • Disclosure of process memory, which may include API keys, tokens and customer data
  • Service crashes affecting digital banking channels
  • Use of compromised services as a foothold into internal networks

6. Recommended actions

6.1 Immediate, within 24 hours

  • Identify every Node.js, Bun, Python and .NET service that decompresses Brotli data from requests or third-party responses. Prioritise internet-facing APIs and webhook handlers.
  • Upgrade the runtime, restart applications, and rebuild container images with updated base images. Rebuild self-contained .NET apps, since they carry their own runtime.
  • Run docker pull before rebuilding, since cached floating tags like node:24 may keep the old version.

6.2 Temporary mitigations, only where patching is delayed

These reduce exposure but are not fixes.

  • Set express.json({ inflate: false }) to reject compressed bodies with a 415. This also rejects gzip, so test clients first.
  • Reject Content-Encoding: br at the proxy or load balancer. This does not cover Brotli responses read by fetch().
  • Audit fetch() calls to servers you don’t control and any direct createBrotliDecompress() use.
  • Run Node.js as an unprivileged user and keep secrets out of the process environment.

6.3 Ongoing

  • Replace end-of-life Node.js lines (20.x and 25.x) with supported versions.
  • Ask third-party software vendors to confirm whether their products bundle Node.js, Bun or an affected Brotli library, and when fixes will be available.
  • Report suspected incidents through the relevant regulatory and national cyber security channels, including the State Bank of Pakistan and National CERT, in line with applicable requirements.

7. Detection and verification

CheckWhat to do
Check versionsRun node -v and bun --version on servers, build hosts, and inside containers. Check Dockerfile base image tags. Digest-pinned images need an image scan. Run pip show brotli brotlicffi in Python environments.
Monitor forShell spawns and unexpected outbound connections from web-facing Node.js processes, and Node.js crashes followed by new program execution in the same workload.
IndicatorsNo reliable public indicators of compromise (file hashes, domains or IP addresses) have been published. Rely on behaviour-based monitoring.
If compromise is suspectedIsolate the affected service, preserve logs, rotate credentials and secrets held by the process, and hunt for persistence. Patching does not remove an attacker who is already inside.

8. How Ciphertronix can assist

ServiceScope
Runtime exposure assessmentIdentification of affected Node.js, Bun, Python and .NET runtimes across servers and containers.
Patch verificationConfirmation that fixed runtimes and rebuilt images are in place.
Compromise assessmentLog and process review of services exposed before patching.
API security testingA controlled review of internet-facing APIs and webhook handlers.

9. References

  • Node.js October 2026 Security Release
  • Google Brotli releases 1.0.10, 1.1.1 and 1.2.1
  • CISA Known Exploited Vulnerabilities Catalogue (entry added 27 October 2026)
  • Microsoft .NET out-of-band security updates, 25 October 2026

Disclaimer. This advisory is provided for information purposes to assist institutions in strengthening their security posture. It is based on information available at the date of issue, and vendor guidance may change. Institutions should evaluate the recommendations against their own environments and regulatory obligations.

Ready to secure and streamline your operations?

Join 30+ enterprise clients who trust Ciphertronix for fraud detection, cyber security and terminal operations. Tell us what you are trying to solve and we will show you the platform running on real data.