TL;DR
Get privacy and security gear delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
The Brotli decoder flaw known as Node2Shell is now confirmed to affect multiple language runtimes and HTTP-related projects, extending the concern beyond Node.js. Patches were available for several projects as of October 23, 2026, but maintainers and users still need to check bundled dependencies and verify their deployed versions.
The Node2Shell Brotli vulnerability has been reported across multiple language runtimes and HTTP-related applications, widening the number of systems that may need updates beyond Node.js. Aikido Security said on October 23 that fixes were available for projects including libbrotli, Python, C++, Node.js, Bun and Envoy, while additional product-specific patch status and remediation remained under review.
The issue is tracked as CVE-2026-111497 and is described in Aikido’s report as an out-of-bounds write in the Google Brotli decoder. The report says versions 1.0.3 through 1.2.0 are affected across platforms. A crafted compressed stream may cause memory corruption; the reported potential consequences include a crash, memory disclosure or arbitrary code execution. Aikido lists a CVSS v4.0 score of 9.2, rated Critical.
The breadth of exposure comes from how Brotli is used: applications may rely on it through a language runtime, an HTTP client or server, or a library bundled into a product. Aikido specifically warns that Python HTTP clients such as requests, httpx and aiohttp may load Brotli packages when installed. It says users should check for Brotli versions at or below 1.2.0 and brotlicffi 1.2.0.x, then upgrade to Brotli 1.2.1 or brotlicffi 1.2.1.0 or later.
Patch availability varies by project and release branch. The report lists fixed Node.js releases 22.23.4, 24.22.1 and 26.12.1; Bun 1.4.4; and Envoy releases 1.40.0, 1.39.3, 1.38.6 and 1.37.8. It also lists fixes in selected Istio releases and patched upstream Brotli versions. These are the versions Aikido reported as fixed on October 23; users should check current vendor guidance, particularly where operating-system packages backport fixes or products bundle their own decoder.
This development matters because a vulnerability in a shared compression decoder can reach systems that do not appear to use Node.js directly. Brotli is used to compress web content, and software that decodes compressed data may include the relevant code as a direct or transitive dependency. That can put HTTP clients, service applications, proxies and other products in scope if they use an affected decoder.
Aikido describes the risk as potentially operating in both directions: a malicious client could target a vulnerable server, while a malicious server could target a vulnerable client that accepts compressed responses. That is the report’s characterization of the flaw, not evidence that any particular deployment has been exploited. The practical concern is that teams may need to inspect dependency trees and product builds, rather than updating one named runtime alone.
Remediation also involves more than changing a package manifest. Aikido advises organizations to update dependency locks, rebuild container images and compiled applications, redeploy, and restart services, then verify that running workloads actually use patched components. If a product bundles Brotli, an operating-system or language-package update may not replace the copy inside that product.
Brotli vulnerability dependency scanning software for CI/CD
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
From Node.js Disclosure to Wider Review
Aikido’s timeline says Node.js disclosed the issue on Wednesday, October 21, 2026, under the name Node2Shell. Python disclosed that Python packages were also vulnerable the following day. On Friday, October 23, Aikido reported that other major languages and HTTP service applications were affected and that patches were not yet fully available across the ecosystem.
The report says OpenAI had found the underlying problem in February and reported it as unauthenticated remote code execution. According to Aikido, the root cause was corrected in the Brotli source code at that time, but it was not recognized as a security issue and no release containing the fix shipped until now. Projects that bundle Brotli therefore need to issue or adopt their own fixed builds.
Exposure is not universal among products that handle web traffic. Aikido says Apache’s standard mod_brotli does not decode Brotli, and its report says Apache and Nginx do not decode it by default. That distinction does not establish the status of every configuration or add-on; administrators should check the actual components and settings in use.
““If there is no patch available for a library or application that may be affected, we recommend disabling Brotli decoding until patches become available.””
— Aikido Security
software composition analysis tool for container image vulnerability scanning
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Which Deployments Still Need Fixes
The full list of affected products and their patch status was still developing in Aikido’s October 23 update. Its report says patches were available for several projects, with more expected, but it does not establish that every HTTP library, proxy, gateway or managed service had been assessed or fixed. It is not yet clear from the supplied material how many deployed systems remain vulnerable or whether any specific product has been exploited.
Aikido also warned that, as of October 23, advisory databases did not map the CVE to the affected PyPI packages. It said pip-audit, Dependabot and Safety might not flag those vulnerable package versions at that point. That status may change; a clean automated scan should not be treated as proof that an application does not include an affected Brotli decoder.
Version numbers may not tell the whole story. Operating-system vendors can backport security fixes without changing the upstream version string, while applications may statically link or bundle a separate copy. Teams need to confirm remediation with the relevant vendor or provider and verify the component running in production.
container security platform for detecting vulnerable dependencies
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Patch, Rebuild and Verify Workloads
Organizations should identify where Brotli decoding is enabled or where the decoder is included as a dependency, then apply the fixed release specified by the runtime, library or product vendor. Aikido lists upstream Brotli 1.2.1 and patched older releases 1.0.10 and 1.1.1, alongside fixed versions for Node.js, Bun, Envoy and Istio. Administrators should use a supported branch and follow vendor security notices for packaged software.
Where no update is available, Aikido recommends disabling Brotli decoding as a temporary measure where possible. After patching, teams should rebuild and redeploy affected images or executables, restart services, and verify the versions in active workloads. For managed services and bundled products, the next step is to seek confirmation from the provider that its fix addresses CVE-2026-111497.
Further updates are expected as maintainers publish advisories and patch additional libraries and applications. The current status is a cross-ecosystem remediation effort; the supplied report does not provide a final inventory of every affected product.
secure software supply chain vulnerability management tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is Node2Shell?
Node2Shell is the name used for CVE-2026-111497, a flaw in the Brotli decoder. Aikido describes it as an out-of-bounds write that can corrupt memory when software processes crafted Brotli-compressed data.
Does the issue affect only Node.js?
No. Aikido reported that the same decoder flaw affects multiple language packages and applications, including Python-related packages and projects such as Bun and Envoy. The actual scope depends on whether a product uses an affected Brotli decoder.
Which Python packages should users check?
Aikido advises checking for Brotli 1.2.0 or earlier and brotlicffi 1.2.0.x. It lists Brotli 1.2.1 and brotlicffi 1.2.1.0 or later as fixed versions. Its report cautions that some Python security scanners did not map the CVE to these packages as of October 23, 2026.
Are Apache and Nginx affected?
Aikido says Apache’s standard mod_brotli does not decode Brotli and that Apache and Nginx do not decode it by default. That does not settle every configuration or separately installed component, so operators should check how their own systems handle Brotli.
What should teams do if they cannot patch immediately?
Aikido recommends disabling Brotli decoding where possible until a fix is available. Teams should also check vendor guidance, then rebuild and redeploy affected applications or images after patching and verify the components running in production.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
