Critical Flaw in Brotli Compression Library Exposes Numerous Software Projects
OpenAI has uncovered a significant security vulnerability in Brotli, a widely adopted compression library that underpins a vast array of software applications. The flaw, which allows for remote code execution, could enable attackers to run unauthorized commands on targeted systems. OpenAI has alerted affected projects, with Node.js among those now issuing security updates.
“Node2Shell” Vulnerability Discovered
The vulnerability, designated CVE-2026-111497 and nicknamed “Node2Shell,” was reportedly identified by OpenAI researchers during internal security assessments of the Brotli decoder. The issue stems from an out-of-bounds write error within the decompression process. Maliciously crafted compressed input can trick the decoder into writing data into unintended memory locations, paving the way for attackers to execute their own code.
High Severity Rating and Broad Impact
The vulnerability has been assigned a critical CVSS score of 9.2, indicating a high severity level that typically prompts urgent action from security teams. The rating is particularly concerning due to the attack’s unauthenticated nature, meaning no login credentials are required. Furthermore, the flaw can affect both client-side and server-side applications, impacting systems that fetch data as well as those that serve it.
Coordinated Response and Patch Releases
Following its discovery, the vulnerability was reported to several key projects, initiating a coordinated disclosure process. Node.js released patched versions 22.23.4, 24.22.1, and 26.12.1 on October 21, 2026. These updates also addressed nine other vulnerabilities, including multiple TLS hostname-check bypasses, making the security release particularly comprehensive.
Broader Ecosystem Affected
Node.js is not the sole project impacted. Bun versions prior to 1.4.4, Envoy, and various Python packages available on PyPI are also vulnerable. Applications that utilize fetch(), Express 5 with body-parser, or directly decompress untrusted Brotli data are at the highest risk.
Exploitation Concerns and Timeline Discrepancy
As of October 23, 2026, there was no widespread public evidence of exploitation. However, proof-of-concept code has since emerged, and researchers at Imperva have demonstrated the vulnerability’s reliable exploitability against affected Node.js builds. An unusual aspect of the timeline is that the fix for the root cause was committed to Brotli’s source code in February 2026, but the vulnerability was not formally disclosed until October 2026. This delay highlights a common challenge in open-source development, where many applications bundle their own copies of libraries like Brotli, necessitating individual updates by each project.
Open Source Challenges and Coordinated Disclosure
The structural complexity of open-source software, where applications often maintain private copies of dependencies, means that an upstream fix is only the initial step. Each project must then integrate the change, release a new version, and ensure users adopt the update. This dynamic underscores the importance of coordinated disclosure, allowing downstream projects like Node.js to prepare fixes before vulnerability details become public.
Urgent Action Required for Engineering Teams
Engineering teams are urged to identify all instances of Brotli within their technology stacks, including bundled copies within runtimes, proxies, and Python dependencies. Teams running Node.js should upgrade to the patched versions 22.23.4, 24.22.1, or 26.12.1. Bun users on versions older than 1.4.4, as well as Envoy and PyPI package users, are also advised to update their software. Prioritization should be given to any service that accepts or fetches compressed data from untrusted sources.
