- 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
| Item | Detail |
|---|---|
| CVE ID | CVE-2026-111497 |
| Name | Node2Shell (also HTTP2Shell, Broccoli2Shell) |
| Component | Google Brotli decompression library, bundled inside Node.js and Bun |
| Severity | Critical. Google, as the CNA, scored it 9.2 (Critical) under CVSS 4.0. Node.js rates it High. |
| Discovered by | Khai Tran and Sylvie Mayer of OpenAI Codex Security found and reported the bug to Node.js. |
| Attack vector | Network. The attack works against applications that decompress Brotli data from untrusted sources. |
| Exploitation status | A 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 decodesbrbodies. - Server-side
fetch(): decompresses Brotli responses when Content-Encoding includesbr, even withAccept-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
| Platform | Affected | Recommended fixed version |
|---|---|---|
| Node.js 26.x | Before 26.12.1 | 26.12.1 |
| Node.js 24.x | Before 24.22.1 | 24.22.1 |
| Node.js 22.x | Before 22.23.4 | 22.23.4 |
| Node.js 25.x and 20.x | Affected; end of life, no fix | Upgrade to a supported line |
| Bun | Before 1.4.4 | 1.4.4 |
| Google Brotli library | 1.0.3 to 1.0.9, 1.1.0, 1.2.0 | 1.0.10, 1.1.1, 1.2.1 |
| Python brotli / brotlicffi | Before 1.2.1 / before 1.2.1.0 | 1.2.1 / 1.2.1.0 |
| .NET runtime | Earlier builds | 8.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 pullbefore rebuilding, since cached floating tags likenode:24may 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: brat the proxy or load balancer. This does not cover Brotli responses read byfetch(). - Audit
fetch()calls to servers you don’t control and any directcreateBrotliDecompress()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
| Check | What to do |
|---|---|
| Check versions | Run 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 for | Shell spawns and unexpected outbound connections from web-facing Node.js processes, and Node.js crashes followed by new program execution in the same workload. |
| Indicators | No reliable public indicators of compromise (file hashes, domains or IP addresses) have been published. Rely on behaviour-based monitoring. |
| If compromise is suspected | Isolate 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
| Service | Scope |
|---|---|
| Runtime exposure assessment | Identification of affected Node.js, Bun, Python and .NET runtimes across servers and containers. |
| Patch verification | Confirmation that fixed runtimes and rebuilt images are in place. |
| Compromise assessment | Log and process review of services exposed before patching. |
| API security testing | A 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.