⚡Megatron LLM Hub
←返回搜索
Website

Brotli 解压库越界写漏洞已遭在野利用,可未授权 RCE

Brotli 1.0.3–1.2.0 广泛嵌入服务端解码链,尚未见到能形成完整防护的策略。
rcecve在野利用
Nov 9, 2026 Node2Shell (CVE-2026-111497): SafeBreach Coverage for the Actively Exploited Brotli RCE Learn how SafeBreach maps CVE-2026-111497 to simulations that test your exposure to Node2Shell’s remote code execution through crafted Brotli-compressed data. Summary What it is: Node2Shell (CVE-2026-111497), also called HTTP2Shell, is an out-of-bounds write in Google’s Brotli decompression library (versions 1.0.3 through 1.2.0) that lets a remote, unauthenticated attacker corrupt memory with a crafted Brotli stream and potentially achieve remote code execution (RCE). Severity and status: Google rates CVE-2026-111497 9.2 Critical under CVSS 4.0. ELLIO recorded Node2Shell exploit traffic in the wild on October 26, 2026, and the Cybersecurity and Infrastructure Security Agency (CISA) added it to the Known Exploited Vulnerabilities (KEV) catalog on October 27, 2026. Who is exposed: Applications that decompress attacker-influenced Brotli data with a vulnerable decoder are at risk, including Node.js 22, 24 and 26, .NET 8, 9 and 10, Bun, Envoy, Istio and Python HTTP clients. How SafeBreach helps: The SafeBreach Exposure Validation Platform includes a new simulation that checks whether your security controls detect or block a crafted Node2Shell Brotli request before it reaches a vulnerable Node.js service, plus existing simulations of generic post-exploitation behavior. Author: Tova Dvorin, Senior Product Marketing Manager What Is Node2Shell? On October 21, 2026, Google and the Node.js project disclosed that the Brotli decoder is vulnerable to an out-of-bounds write that can lead to remote code execution. Tracked as CVE-2026-111497 and nicknamed Node2Shell, the flaw lets a remote, unauthenticated attacker corrupt process memory by getting a vulnerable application to decompress a crafted Brotli stream. Brotli is Google’s compression format and one of the standard ways web servers and clients compress HTTP traffic (Content-Encoding: br). Its C decoder is embedded in language runtimes, proxies, data platforms and industrial software. The Node2Shell bug lives in that decoder (c/dec/decode.c) in Brotli versions 1.0.3 through 1.2.0, a range that ELLIO traces back to the 1.0.3 release in March 2018. The root cause is an unchecked return value (CWE-252) that leads to an out-of-bounds write (CWE-787) . According to the Node.js security release , “an invalid block switch was reported as a temporary need for more input instead of a permanent format error, so the streaming decoder kept appending input bytes to an eight-byte internal buffer.” Past the eighth byte, attacker-supplied data overwrites adjacent decoder memory. The fix makes the decoder stop with a hard format error instead. Exploitation requires no authentication and no user interaction. The one prerequisite is that the target decompresses Brotli data the attacker can influence. In Node.js, that includes request bodies parsed by Express 5 or body-parser 2 when sent with Content-Encoding: br, server-side fetch() responses, and direct node:zlib calls on untrusted input. A bare Node.js HTTP server does not decompress request bodies on its own. Three details set Node2Shell apart: The fix was public long before the advisory. ELLIO reports the fix was written on February 27, 2026, and sat in Brotli’s public source repository with no release and no advisory for eight months. Anyone reading the commit history had a head start. Exploitation is practical, if not one-shot. The Imperva Red Team demonstrated code execution against the official, unmodified Node.js 24.22.0 Linux arm64 image, and ELLIO reproduced shells on default x86-64 builds. Each build needs its own memory offset. It is already in the wild. ELLIO recorded exploit traffic against Node.js 24.22.0 on October 26, 2026, from an IP address previously seen in mass-exploitation campaigns. CISA added CVE-2026-111497 to the KEV catalog the next day, with a November 10, 2026 deadline for US federal agencies. OpenAI Codex Security researchers Khai Tran and Sylvie Mayer reported the flaw to Node.js. It also circulates as HTTP2Shell and Broccoli2Shell. Why Node2Shell Matters When a vulnerability like this drops, the predictable response is to patch Node.js and move on. That response makes sense, but it’s a partial answer, for two reasons. First, Node2Shell is a library flaw before it is a Node.js flaw. The NVD record lists affected configurations across Node.js, .NET, Bun, Envoy, Istio, Python’s brotlicffi, the Go Brotli port, Apache Arrow, ClickHouse, DuckDB, 7-Zip forks, the TianoCore EDK II firmware project and several Siemens Industrial Edge products. Many of these ship their own copy of the decoder, so patching the operating system’s Brotli package does not fix a runtime, container image or compiled binary that bundles its own. Embedded copies are the kind of exposure that lingers for years, much like the decade-old CVEs still being used to breach networks in 2026 . Second, the real risk is what an attacker does once they have a foothold. A realistic attack chain looks like this: An attacker sends a crafted, Brotli-compressed request body to an internet-facing API that decompresses it. ELLIO’s in-the-wild sample was a single 23 MB request. Most attempts crash the worker process. Process managers and container orchestrators restart it automatically, which gives the attacker another try. A successful attempt returns a shell running as the service’s own account, with whatever secrets and cloud credentials that account can reach. From there, the attacker can download tooling, steal tokens, move laterally into the cluster or cloud account, or deploy cryptominers and ransomware. Outbound traffic is exposed too. An application that uses server-side fetch() to retrieve content from a server the attacker controls can receive the malicious payload in the response, and request-filtering stopgaps don’t cover that path. The closest comparison is Log4Shell in 2021. Both are flaws in a ubiquitous library that most teams never chose directly, and both turned “are we patched?” into “where is this thing running?” The question security teams should be asking is no longer “Are we vulnerable to Node2Shell?” Instead, it’s “If an attacker exploits CVE-2026-111497 tomorrow, can our security controls detect and stop them before damage is done?” SafeBreach Coverage for Node2Shell SafeBreach Labs validated and integrated detection for CVE-2026-111497, available in the SafeBreach CTEM Platform . Existing Behavioral Coverage SafeBreach has existing behavioral coverage for what an attacker does after a foothold. These are generic post-exploitation simulations, not Node2Shell-specific content, and they test your controls no matter which vulnerability gave the attacker initial access. They include: Web shell deployment [SIMULATION ID: NOAM TO CONFIRM] Rogue certificate authority (CA) installation [SIMULATION ID: NOAM TO CONFIRM] These simulations are mapped to MITRE ATT&CK and can be used immediately to validate detection and response capabilities across your infrastructure. New Simulation Coverage To address CVE-2026-111497, the SafeBreach Labs team has added one new simulation: #11843: Node2Shell Brotli Decoder Vulnerability CVE-2026-111497 Detection (WAF) , which runs over both HTTP and HTTPS Simulation #11843 is an exposure check rather than an exploit. It confirms whether a crafted Brotli request reaches a vulnerable Node.js service. It is also an Advanced Action, so it is scheduled differently from a standard simulation. Expected behavior: The simulation sends the crafted Brotli request, and the result shows whether your security controls detected or blocked it before it reached the service. It is a detection and exposure outcome, so it does not open a shell or execute code on the target. How to Test Your Defenses Against Node2Shell with SafeBreach SafeBreach customers can now validate their security controls against CVE-2026-111497 in two ways. Whichever you choose, note that simulation #11843 is an Advanced Action, so it is scheduled differently from a standard simulation. Method 1 – SafeBreach Scenarios: Navigate to the SafeBreach Scenarios page and choose the dedicated Node2Shell (CVE-2026-111497) Detection scenario or the broader Node.js October 2026 Security Release – Behavioral + CVE detection scenario. Method 2 — Known Threats Series: Open the Known Threats Series report, select the Node2Shell (CVE-2026-111497) Detection report, and run the simulations. Remediation and Recommendations Patch: Upgrade Node.js to 22.23.4, 24.22.1 or 26.12.1, released October 21, 2026. Node.js 20.x, 23.x and 25.x are end of life and will not receive a fix. Google released Brotli 1.0.10, 1.1.1 and 1.2.1 the same day, and Microsoft shipped .NET 8.0.33, 9.0.22 and 10.0.14 on October 25, 2026. Other fixed releases include Bun 1.4.4, Python Brotli 1.2.1, brotlicffi 1.2.1.0, Envoy 1.36.12, 1.37.8, 1.38.6, 1.39.3 and 1.40.0, and Istio 1.29.9, 1.30.6 and 1.31.2. Rebuild container images and Bun-compiled executables, and rely on vendor advisories for Linux distribution packages, which often backport the fix under older version numbers. Detect: Watch for web-facing worker processes that exit with a segmentation fault (exit code 139) right after receiving Brotli-encoded data, repeated crash-and-restart loops, and processes pinned at 100% CPU inside a decompression call, as Datadog Security Labs describes. The strongest signal is behavioral: a Node.js or other web process spawning a shell, redirecting a network socket to standard input or output, or opening unexpected outbound connections. Log the Content-Encoding header on inbound requests so Brotli-encoded bodies are visible. Mitigate: If you can’t patch immediately, reject request bodies sent with Content-Encoding: br at your reverse proxy, load balancer or web application firewall (WAF). This stopgap does not protect Brotli responses that your applications fetch, and Node.js has published no workaround, so upgrading remains the only complete fix. Uninstall the Python Brotli and brotlicffi packages where they aren’t needed, and disable the Brotli decompressor in Envoy where it is configured. Then use the two methods above to confirm your controls catch Node2Shell requests and the post-exploitation behavior that follows, rather than assuming they do. Stay Ahead with SafeBreach Node2Shell is a reminder that the most dangerous dependencies are often the ones nobody remembers choosing. Patching Node.js is necessary, but it doesn’t answer whether every embedded copy of Brotli is gone, or whether your controls would catch an attacker who got a shell first. SafeBreach customers can use the simulation content above to check today whether their controls detect or block Node2Shell requests and catch what an attacker does next. About the Author Tova Dvorin is currently the Senior Product Marketing Manager at SafeBreach. She has 8 years of Product Marketing experience in the cybersecurity sector, after a previous career as a war journalist. Frequently Asked Questions What is CVE-2026-111497 (Node2Shell)? CVE-2026-111497, nicknamed Node2Shell, is an out-of-bounds write in Google’s Brotli decoder. A crafted Brotli-compressed stream causes the decoder to write past an eight-byte internal buffer, which can crash the process, leak memory or allow remote code execution. Google and the Node.js project disclosed CVE-2026-111497 on October 21, 2026, after OpenAI Codex Security researchers reported it. Is HTTP2Shell the same as Node2Shell? Yes. HTTP2Shell, Node2Shell and Broccoli2Shell are all names for CVE-2026-111497, the out-of-bounds write in Google’s Brotli decoder. Node2Shell was the first name to circulate, and HTTP2Shell and Broccoli2Shell followed as the impact on .NET, Bun, Envoy, Istio and Python HTTP clients became clear. All three names point to the same CVE record and the same fixed versions. Which systems and versions are affected by CVE-2026-111497? CVE-2026-111497 affects Google Brotli 1.0.3 through 1.2.0 and any software that embeds it. Affected platforms include Node.js 22, 24 and 26 before the October 21, 2026 releases, end-of-life Node.js 20, 23 and 25, .NET 8, 9 and 10, Bun before 1.4.4, Envoy, Istio, and Python’s Brotli and brotlicffi packages. Applications are at risk when they decompress attacker-influenced Brotli data. How severe is CVE-2026-111497, and is it being exploited? CVE-2026-111497 is rated 9.2 Critical under CVSS 4.0 by Google and 9.8 Critical under CVSS 3.1 by NVD. A public proof of concept appeared on GitHub on October 22, 2026. ELLIO recorded Node2Shell exploit traffic in the wild on October 26, 2026, and CISA added CVE-2026-111497 to its Known Exploited Vulnerabilities catalog on October 27, 2026. Is there a patch for CVE-2026-111497? Yes. Node.js 22.23.4, 24.22.1 and 26.12.1 and Google Brotli 1.0.10, 1.1.1 and 1.2.1 fix CVE-2026-111497 and were released on October 21, 2026. Microsoft fixed .NET in 8.0.33, 9.0.22 and 10.0.14 on October 25, 2026. Bun 1.4.4, brotlicffi 1.2.1.0 and updated Envoy and Istio releases are also available. Node.js 20, 23 and 25 will not be patched. Is there a workaround for Node2Shell if I can’t patch right away? There is no complete workaround for Node2Shell. The most common stopgap is rejecting request bodies sent with Content-Encoding: br at the reverse proxy, load balancer or web application firewall, but that does not protect Brotli responses an application fetches. Node.js has published no workaround for CVE-2026-111497, so upgrading the runtime remains the only complete fix. How can organizations test their exposure to CVE-2026-111497? Organizations can test their exposure to CVE-2026-111497 by sending a crafted Node2Shell Brotli request through their own defenses and checking whether security controls detect or block it before it reaches the service. In the SafeBreach CTEM Platform , customers can select the Node2Shell (CVE-2026-111497) Detection scenario on the SafeBreach Scenarios page or run the CVE-2026-111497 report in the Known Threat Series. You Might Also Be Interested In Research Blog Live Exploitation for PHP2Shell (CVE-2026-109618, CVE-2026-109619): SafeBreach Coverage for the CISA PHP Alert Read More Solution Brief SafeBreach CTEM Platform Download the CTEM Platform Brief Podcast Videos Beyond CVEs: Why Patching Isn’t Enough to Stop Breaches Listen Now Get the latest research and news