Node.js Vulnerable to RCE via Crafted Brotli Data (Node2Shell)
A critical remote code execution vulnerability, dubbed Node2Shell (CVE-2026-111497), has been discovered in Node.js, allowing attackers to execute arbitrary code on official Linux builds using specially crafted Brotli compressed data.

Security researchers at Imperva have demonstrated a critical remote code execution (RCE) vulnerability within Node.js, officially designated as CVE-2026-111497 and nicknamed "Node2Shell." The exploit leverages specially crafted Brotli compressed data to achieve arbitrary code execution on official Linux arm64 builds of Node.js version 24.22.0. This attack vector bypasses the need for custom builds or debuggers, making it a significant threat to applications handling untrusted Brotli data.
The vulnerability resides in the Brotli decoder bundled with Node.js. Researchers successfully executed their proof-of-concept by feeding malformed Brotli data to the decoder, causing it to enter an invalid state and overwrite memory. This out-of-bounds write, triggered by an impossible point in the Brotli stream, allows an attacker to inject and run their own code. While Imperva's demonstration required several attempts on their specific Linux arm64 setup, the patched version, Node.js 24.22.1, successfully rejected the malicious data, preventing code execution.
Node.js officially disclosed the flaw and released patches on October 21, urging all applications that decode untrusted Brotli data to update immediately. The vulnerability affects Node.js versions 22.x, 24.x, and 26.x, as the Brotli decoder is a shared component across these lines. This means a wide range of applications, including those using Express 5's body parsers or Node.js's built-in fetch() for handling Brotli-compressed responses, are potentially vulnerable.
Imperva's proof-of-concept successfully demonstrated code execution through both request-body and response paths. They tested this against Express 5.0.0 to 5.3.0 and body-parser 2.0.0 to 2.3.0, confirming the exploit's efficacy in common web application middleware. While the initial public proof-of-concept only achieved code execution on a deliberately weakened test build, Imperva's work shows a viable attack against standard, official Node.js builds.
As of October 22, no exploitation of this vulnerability in the wild has been reported. However, the potential for widespread impact necessitates prompt action from developers and system administrators. The Node.js team addressed the flaw by importing an upstream Brotli patch that ensures the decoder halts with a format error when encountering malformed data, rather than continuing in an unstable state.
Node.js has released patched versions for its supported lines, and users are strongly advised to update to these releases. For older, end-of-life versions (20.x and earlier), migration to a supported Node.js line is the only solution, as these versions will not receive the fix. There is no workaround within Node.js itself, meaning applications unable to update immediately are left without a runtime-level mitigation.
While Node.js itself does not offer a workaround, Imperva suggested limiting untrusted Brotli traffic on affected application paths where feasible. They also implemented protective rules in their own Web Application Firewall (WAF) to detect and block attacks based on their findings. Vercel, a popular Node.js hosting platform, has also deployed rules to block such attacks in inbound requests, though these do not cover Brotli responses fetched from external servers and do not negate the need for updating Node.js.
The Node2Shell vulnerability highlights the ongoing risks associated with bundled libraries and the importance of keeping software, including development runtimes, up-to-date. The ability to achieve RCE through seemingly innocuous data compression formats underscores the need for robust input validation and timely patching across the software supply chain.
The new article provides further technical details on the Node2Shell exploit, demonstrating a standalone proof of concept that successfully executed code on an official Node.js 24.22.0 Linux arm64 image. It elaborates on how the vulnerability is triggered by an invalid transition in the Brotli stream, leading to an out-of-bounds write, and confirms that the patched Node.js 24.22.1 release rejects these malicious inputs.
This new article expands on the Node2Shell vulnerability (CVE-2026-111497) by detailing its impact beyond Node.js, affecting widely used software such as Bun, Python's Brotli and brotlicffi packages, and Envoy proxies. It highlights that while Node.js has seen a proof-of-concept exploit, exploitation in other affected software has not been demonstrated, and no real-world attacks have been reported across the board.
New research indicates that the HTTP2Shell vulnerability (CVE-2026-111497), initially identified in Node.js, has a broader impact. The flaw, rooted in Google's Brotli decoder, has now been shown to affect .NET, FFmpeg, ClickHouse, and Apache Arrow, leading to crashes, memory corruption, and denial-of-service conditions. Microsoft has already released updates for .NET, while other affected projects are in the process of patching.
Microsoft has released security updates for its .NET, Visual Studio, and PowerShell products to address the Node2Shell vulnerability (CVE-2026-111497). This critical out-of-bounds write flaw in Google's Brotli decompression library, which can lead to remote code execution, was previously patched in Node.js and several Python packages. Microsoft's advisory rates the vulnerability as critical for .NET and Visual Studio, with an exploitability assessment of 'Exploitation More Likely'.
Microsoft has released an out-of-band update addressing a critical buffer overflow vulnerability (CVE-2026-111497) in its .NET developer platform, affecting versions 8 through 11. This flaw, present in the Brotli decompression algorithm, could allow unauthenticated attackers to read or corrupt process memory, leading to information disclosure, denial of service, or privilege escalation. The update also includes fixes for another new vulnerability (CVE-2026-114148) and re-issued patches for two previously disclosed flaws from Microsoft's October Patch Tuesday.
Microsoft has released out-of-band security updates for .NET versions 8 through 11 to address CVE-2026-111497, a Brotli decompression buffer overflow that could allow unauthenticated attackers to read or corrupt memory. This vulnerability affects applications handling Brotli-compressed data through ASP.NET Core request decompression, HttpClient automatic response decompression, or System.IO.Compression Brotli APIs, though Microsoft notes that request and automatic response decompression are not enabled by default. The update also completes fixes for CVE-2026-70197 and CVE-2026-102870, and addresses CVE-2026-114148 related to unsafe ownership metadata in Linux .NET tarballs.
Microsoft has now released an out-of-band update for its .NET platform (versions 8, 9, 10, and 11) to address CVE-2026-111497, a critical buffer overflow vulnerability within Google's Brotli compression library. This critical flaw, rated 8.1 CVSS v3.1, allows unauthenticated attackers to corrupt process memory, potentially leading to information disclosure, denial of service, or privilege escalation. While exploits are reportedly possible and have been demonstrated, there is no current evidence of widespread exploitation by malicious actors, though Microsoft's advisory assesses exploitation as "More Likely."
PHP has released updated Windows packages for versions 8.2 through 8.5 to address CVE-2026-111497, a critical flaw in the Brotli compression library that could lead to memory corruption and remote code execution. This vulnerability is exploitable via the cURL extension when automatic decompression of HTTP responses is enabled, a feature that is off by default but can be activated by applications like Guzzle. The new builds, identified by a '-1' suffix in their filenames and updated SHA-256 hashes, incorporate the fixed Brotli 1.2.1 version and retain previous security fixes.
This Tenable blog post provides a comprehensive FAQ for CVE-2026-111497, also known as Brotli2Shell, detailing its impact across various software like Node.js, .NET, and Envoy Proxy. It clarifies that while patches are available for Brotli and major runtimes, applications bundling their own Brotli copies require individual fixes, and highlights that some projects had not yet shipped fixed releases as of October 26th.
This new reporting expands on the Node2Shell vulnerability (CVE-2026-111497) by detailing its widespread impact beyond Node.js. The Brotli compression library, which is the root cause, is used by numerous other applications including .NET, Bun, Envoy Proxy, Istio, Python HTTP clients, FFmpeg, Apache Arrow, and ClickHouse. Furthermore, the article confirms that exploit traffic for CVE-2026-111497 has been observed in the wild, with threat actors actively leveraging a public proof-of-concept exploit.
CISA has also added CVE-2026-48356, an Adobe Commerce and Magento vulnerability enabling unrestricted file uploads, to its Known Exploited Vulnerabilities (KEV) Catalog. This addition is based on evidence of active exploitation, highlighting a new attack vector for threat actors targeting e-commerce platforms.
Sweet Security is now offering its runtime Virtual Patching protection, named Sweet Safety Net, free of charge for 30 days to all organizations impacted by the HTTP2Shell vulnerability (CVE-2026-111497). This proactive measure aims to block exploitation attempts immediately, providing a crucial window for organizations while permanent fixes are developed and deployed for the Brotli decoder flaw affecting multiple frameworks.
The Brotli vulnerability, previously detailed as affecting Node.js (CVE-2026-111497), has now been confirmed to extend its impact beyond Node.js. Researchers have indicated that the flaw in Google's compression library affects a broad range of software, highlighting a wider potential attack surface than initially understood.