Skip to content

Image: zscaler.com · rights & removal

Executive Summary

A critical vulnerability, CVE-2026-111497, has been disclosed within the Brotli decoder, affecting software packages such as Node.js, Bun, .NET, Envoy Proxy, and others. This out-of-bounds write flaw, also known as Node2Shell or HTTP2Shell, carries a CVSS 4.0 score of 9.2 and can potentially lead to remote code execution (RCE) if an attacker can coerce a vulnerable process to decompress malicious data. The attack vector can operate via inbound requests, such as those containing `Content-Encoding: br`, or outbound responses received by a vulnerable client. Recommendations stress immediate patching of affected runtimes and libraries, rebuilding containers with patched images, or disabling Brotli decoding as a short-term mitigation.
Observations from Zscaler Deception indicate active reconnaissance and exploitation attempts targeting this vulnerability shortly after its public disclosure, with recorded events involving unique malformed Brotli payloads. The threat necessitates validating each vulnerable component independently, as general system-level updates may not cover statically bundled decoders. Organizations are urged to proactively monitor for suspicious activity, including unexpected crashes or abnormal memory access in components utilizing Brotli decompression.

Facts Only

CVE-2026-111497 is an out-of-bounds write vulnerability in Google’s Brotli decoder.
The vulnerability is known as Node2Shell and HTTP2Shell.
The CVSS 4.0 score is 9.2 (Critical).
Exploitation can result in process crashes, memory disclosure, or RCE.
Vulnerable software includes Node.js, Bun, Python Brotli bindings, .NET, Envoy Proxy, and libbrotli.
Exploitation can occur via inbound traffic (malicious request bodies) or outbound traffic (malicious responses).
Patches include Node.js 24.22.1 for versions up to 24.22.0.
Zscaler Deception observed exploitation attempts involving this CVE within 24 hours of disclosure.
Malicious payloads included truncated JSON Brotli and 22-byte/23-byte invalid block-switch seeds.
Recommendations include patching, rebuilding containers, and monitoring for process crashes.

Full Take

The narrative functions primarily as a timely threat advisory delivered through a vendor's platform, blending technical vulnerability disclosure with a marketing call to action. Its strongest persuasive push centers on urgency—the immediate observation of real-world exploitation attempts by ThreatLabz—to compel rapid adoption of the vendor’s security stack. This urgency frames the complex technical remediation process (patching specific runtimes, rebuilding containers) as an immediate race against active adversaries.
The core assumption underpinning this advisory is that operational obscurity is inherently fragile; any exposure to untrusted data streams represents a critical risk, which justifies the aggressive mitigation strategies presented. While the technical details of the flaw—a failure to validate return values in the block-decoding logic—are sound, the emphasis placed on Zscaler’s detection capabilities (ZPA App Protection, Deception decoys) functions as a strong vector of Authority Game. The vendor’s proprietary observation data serves not only to warn but to establish the necessity of purchasing or deploying their specific coverage tools.
The systemic pattern here echoes the perpetual security arms race: a vulnerability is found, a vendor quickly characterizes the risk (Critical), demonstrates threat presence (Deception logs), and offers the pathway to mitigation (their specific product feature sets). The cost bearer is the organization whose legacy or insufficiently segmented architecture makes rapid patching impossible, leaving them exposed until they can implement defensive layering.
Patterns detected: ARC-0060 Authority Game, ARC-0021 Fear Appeal.
How can organizations realistically achieve deep visibility into all dynamically loaded, statically bundled, or third-party instances of Brotli decoding across heterogenous microservice landscapes without an overarching control plane? If the primary defense is rapid patching, what is the acceptable temporal boundary before a "Critical" threat demands a disruptive operational halt? What architectural investments shift the focus from reactive patching to inherent resilience against protocol-level abuse?

From the original · Zscaler ThreatLabz

Zscaler Blog Get the latest Zscaler blog updates in your inbox CVE-2026-111497: Node2Shell / HTTP2Shell Vulnerability May Allow RCE Introduction On October 21, 2026, the Node.js project disclosed CVE-2026-111497, an out-of-bounds write vulnerability in Google’s Brotli decoder used by Node.js and other software. The vulnerability is also known as Node2Shell and more recently as HTTP2Shell.
Read the full story at zscaler.com

Sentinel unavailable

The automated check of the source article's wording did not complete, so no result is shown.

This looks only at the wording of the original source article, not at this page's AI-written sections. A small local AI model made this estimate. It has not been checked against known human and machine texts, so treat it as provisional. It cannot show who wrote an article.

CVE-2026-111497: Node2Shell / HTTP2Shell Vulnerability May Allow RCE | Huntaegis