Robotics

Node2Shell Brotli Flaw Triggers Industry Patches

A critical out-of-bounds write vulnerability in Google's Brotli compression library has prompted swift patching across major platforms, including Microsoft, Node.js, and Python packages.

Radwan AbdulhadiEditor and technology writer

Published: October 26, 2026 · Updated: October 26, 2026 · 3 min read

Node2Shell Brotli Flaw Triggers Industry Patches — Image: SecurityWeek

Overview of the Node2Shell Vulnerability

A severe security vulnerability affecting Google’s Brotli data compression library has triggered widespread patching across the technology industry. Tracked as CVE-2026-111497 and widely referred to as Node2Shell, the flaw involves an out-of-bounds write issue within the Brotli decoder, which is embedded in numerous applications and libraries. Google assigned the vulnerability a critical CVSS v4 score of 9.2, impacting software utilizing Brotli versions 1.0.3 through 1.2.0.

According to technical breakdowns, specially crafted input can push data beyond the limits of the buffer utilized by the decoder. This memory corruption can cause process crashes, leak memory contents, or allow an unauthenticated attacker to run arbitrary code. Fixed versions of the library include Brotli 1.0.10, 1.1.1, and 1.2.1.

Discovery and Prior Source Code Fixes

The vulnerability's discovery was credited to members of OpenAI Codex Security. OpenAI stated that the issue came to light during red-teaming operations, after which the company notified the Brotli developers and downstream projects relying on the library. Interestingly, the root cause issue was addressed in the Brotli source code as early as February, but developers were unaware at the time that it posed a security vulnerability, and no newer release of Brotli had been issued until recently.

Guidance and details regarding the issue have been compiled by security initiatives, including insights shared through an official advisory published by OpenAI's Patch the Planet initiative.

Microsoft and Python Package Updates

Following initial patches from the Node.js project and Python package maintainers last week, Microsoft rolled out updates on October 25. Microsoft's fixes targeted .NET runtime versions 8.0.33, 9.0.22, and 10.0.14, alongside .NET 11 Release Candidate 3, Visual Studio 2019, 2022, and 2026, and PowerShell versions 7.4, 7.5, and 7.6. Microsoft categorized the vulnerability as an elevation of privilege issue with a CVSS v3.1 base score of 8.1, rating it critical for .NET and Visual Studio while assessing its exploitability as 'Exploitation More Likely.'

In the Python ecosystem, the vulnerable decoder is integrated directly into two PyPI packages, Brotli and brotlicffi. Both have received patches via the release of versions 1.2.1 and 1.2.1.0 respectively, mitigating risks for Python-based applications.

Code Execution Potential and Security Firm Findings

Security researchers have evaluated the real-world impact of Node2Shell. Imperva demonstrated that the vulnerability could be exploited for code execution on the official Node.js 24.22.0 image for Linux arm64. By transmitting malicious data in server responses or request bodies processed by Express 5 or body-parser 2, researchers established code execution for tested Linux arm64 configurations, though proofs did not succeed on every single attempt and the firm chose not to make its exploit public.

Additional insights regarding how the flaw can be leveraged have been discussed across the cybersecurity community, including analyses by researchers who have reportedly analyzed the mechanics of the Node.js vulnerability.

Mitigation and Ongoing Ecosystem Impact

Attacks leveraging Node2Shell require malicious Brotli data to successfully reach the decoder, such as through libraries that unpack compressed content on behalf of applications. Vulnerabilities may affect compressed HTTP request bodies, responses retrieved from untrusted servers, and compressed files.

To secure systems completely, administrators must apply software updates, restart affected services, and rebuild container images on top of newly patched base environments, because running processes continue utilizing the vulnerable code until restarted.