CISA Warns of Actively Exploited Node2Shell RCE Flaw Affecting Node.js Servers

The Cybersecurity and Infrastructure Security Agency (CISA) has added CVE-2026-111497, known as Node2Shell, to its Known Exploited Vulnerabilities catalog following evidence of active exploitation.

Added October 27, 2026, the vulnerability carries a November 10 remediation deadline for federal civilian agencies. It affects Google’s Brotli decoder, including copies bundled with Node.js.

Google rates the vulnerability Critical, with a CVSS 4.0 score of 9.2. Unauthenticated attackers can supply crafted Brotli streams to corrupt memory, disclose sensitive information, crash applications, or potentially execute arbitrary code.

CISA Warns of Actively Exploited Node2Shell RCE Flaw

The issue is also called HTTP2Shell and Broccoli2Shell. The vulnerability stems from incorrect handling of an invalid Brotli block switch.

Instead of reporting a permanent format error, the decoder treats the condition as a temporary shortage of input. Subsequent streaming calls keep appending bytes to an eight-byte internal buffer without draining it, eventually writing beyond its boundaries.

Fixed and affected (Source: ellio)
Fixed and affected (Source: ellio)

The flaw combines CWE-252, unchecked return value, with CWE-787, out-of-bounds write. Upstream commit 0ed4268a changes block-switch helpers to return explicit decoder error codes.

Invalid switches now produce BROTLI_DECODER_ERROR_FORMAT_BLOCK_SWITCH, error -17, terminating decompression rather than requesting additional input.

Exposure depends on whether attacker-controlled data reaches Brotli decompression. A basic Node.js HTTP server does not automatically decompress request bodies.

However, Express 5 body parsers and Koa middleware can process requests containing Content-Encoding: br before route handlers execute.

Built-in fetch() and other HTTP clients also expose applications when they decompress malicious responses from attacker-influenced destinations.

ELLIO reproduced remote code execution on official Node.js 24.22.0 x86-64 builds across four configurations: plain HTTP with explicit decompression, the official slim container, Express 5.3.0, and Koa 3.

Tests retained address space layout randomization, and resulting shells inherited the service account’s privileges. On October 26, ELLIO observed a 23,069,983-byte exploit request from 94.154.43.7, targeting Node.js 24.22.0.

Visitor session (Source: ellio)
Visitor session (Source: ellio)

CISA said although its delivery structure matched public tooling, the captured payload’s custom execution chain failed in 50 laboratory attempts.

This distinguishes observed exploitation attempts from demonstrated successful compromises. Failed attempts can nevertheless crash workers and disrupt availability.

Administrators should upgrade to Node.js 22.23.4, 24.22.1, or 26.12.1, or newer supported releases. End-of-life branches 20.x, 23.x, and 25.x require migration.

Brotli fixes are available in 1.0.10, 1.1.1, and 1.2.1. Separately update affected dependencies, rebuild container images, and restart services. Do not rely on process.versions.brotli: patched Node.js builds can still report 1.2.0.

Temporarily rejecting inbound Brotli bodies reduces one exposure path but does not address malicious outbound responses. Monitor decoder crashes and restrict access to core dumps containing potentially sensitive process memory.

Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team 

Tamilselvan
Tamilselvanhttps://cyberpress.org/
Tamilselvan is an Investigative cybersecurity journalist dedicated to breaking stories on ransomware cartels, data breaches, and state-sponsored espionage.

Trending News

Related Stories