Google Brotli Decoder Vulnerability CVE-2026-111497 Enables Remote Code Execution in Node.js, Python, Bun and Envoy
Google Brotli decoder has been found to contain a serious memory corruption vulnerability tracked as CVE-2026-111497. The flaw impacts Node.js, Python, Bun, Envoy and any other software that embeds the official Google Brotli implementation.
What is Brotli and why the impact is so broad
Brotli is a compression format developed by Google and now used for the majority of web traffic to reduce bandwidth and improve page-load times. Because it is part of the modern web standard, virtually every major web server, CDN and proxy relies on the same upstream decoder code. Node.js ships Brotli support natively, Python provides the brotli and brotlicffi packages, the Bun JavaScript runtime includes it by default, and the Envoy cloud-native proxy uses it when Brotli decompression is enabled.
The vulnerability is an Out-of-Bounds Write. An attacker who supplies a malicious Brotli-compressed payload can cause the decoder to write beyond allocated buffers, corrupting adjacent memory. Possible outcomes include denial of service, sensitive data leakage and, most critically, remote code execution.
Node2Shell: Imperva proves RCE on official Node.js builds
Researchers at Imperva successfully weaponized the flaw on unmodified Node.js 24.22.0 (Linux arm64). They named the technique Node2Shell. The exploit works by feeding specially crafted Brotli data to functions such as zlib.brotliDecompress. Although reliability is not 100 percent and multiple attempts may be required, the attack succeeds on a stock release without any debugging symbols or weakened mitigations.
The same payload is blocked on the patched Node.js 24.22.1 release, confirming that the fix is effective. Earlier public proofs-of-concept only worked on deliberately weakened test builds; this demonstration on production binaries significantly raises the risk profile.
Affected software and remediation guidance
- Node.js 22.x below 22.23.4, 24.x below 24.22.1, 26.x below 26.12.1
- Python brotli and brotlicffi packages (all versions)
- Bun all releases that include the built-in Brotli decoder
- Envoy any deployment with Brotli decompression filters enabled
Administrators should immediately upgrade Node.js to the fixed releases listed above and restart all processes. Python users must wait for updated brotli packages or implement temporary input-size validation. Bun and Envoy users should monitor official channels for patches and consider disabling Brotli decompression until fixes are available.
Supply-chain lessons
The incident once again illustrates how a single upstream library can expose an entire ecosystem. Similar patterns were observed with Log4Shell and the xz-utils backdoor. Organizations are advised to maintain software bill-of-materials (SBOM) records, enable automated dependency updates via tools such as Dependabot, and apply defense-in-depth controls around any decompression routines.
Related articles
Four Characters Bypass SSRF Filter: IPv6 Zone and netip.Prefix.Contains in Go
A vulnerability tracked as CVE-2026-126799 affects Gotenberg versions 8.31.0 through 8.37.0 and allows attackers to bypass SSRF protections by appending an IPv6 zone identifier to addresses such as [::%251]. The flaw stems from how Go's net/netip package handles zone information in methods like Prefix.Contains and IsUnspecified, which ignore or mishandle the zone component. Researchers reproduced the issue on Go 1.26.11 and 1.27.4, showing that addresses with zones like ::%1 or fec0:1234::3%eth0 evade common allow-list checks used in webhooks, link previews, and URL proxies. The root cause lies in documented behavior where netip.Prefix.Contains returns false for any address carrying a zone, while some methods like IsLoopback remain zone-agnostic. Fixes include stripping the zone with WithZone before classification, rejecting zones in URLs outright, and adding a second check inside net.Dialer.Control. The same pattern appears in many Go projects, making the issue broader than a single Gotenberg bug.
Researchers Disclose Full Remote Vehicle Takeover Chain in Major Automaker Connected Platform
Security researchers Shubs and Sam Curry discovered a complete attack chain allowing remote control of any connected vehicle from a major undisclosed automaker across Australia and other large markets. The chain began with decompiled Android APK analysis that revealed hardcoded API endpoints under redacted-telematics.com.au and exposed administrative interfaces. Weak access controls in an OpenIDM instance permitted unauthenticated enumeration of user accounts via email, GUID, and phone number lookups. Path traversal bypasses combined with leaked staging credentials granted administrative access to ForgeRock OpenIDM, enabling password resets and full account takeover. Researchers further bypassed MFA using Resource Owner Password Credentials flows and obtained valid mobile application tokens. With these tokens they could issue arbitrary remote commands including unlock, lock, horn activation, and engine start to any vehicle by VIN or license plate.
Nightmare Eclipse Publishes SignDrop Zero-Day in Windows CLFS Driver
Security researcher Abdelhamid Naseri, known as Nightmare Eclipse, has disclosed a new zero-day vulnerability named SignDrop affecting the Common Log File System (CLFS) driver in Windows. The flaw allows attackers to bypass authentication protections introduced by Microsoft in October 2025 and escalate privileges on affected systems. SignDrop exploits the way CLFS handles .cnpf authentication file creation when a new log file is generated, enabling a privileged process to open the file later and create it with SYSTEM rights. The technique can also be abused against any antivirus or EDR engine to disable self-protection mechanisms by making file creation requests appear to originate from the legitimate security process itself. Nightmare Eclipse confirmed the issue works on Windows 11 26H2, Windows 11 26H2 Experimental, and Windows Server 2025 Experimental, impacting an estimated 80 percent of Windows installations. No workaround exists other than waiting for a Microsoft patch, as disabling CLFS protections would reintroduce memory corruption risks. The researcher previously released multiple other zero-days, including BigDiskBuster and RoguePlanet targeting Microsoft Defender.
Telegram Patches RCE Vulnerabilities in HTML Widgets After Researcher Demonstrates Calculator Exploit
Telegram introduced HTML widgets for bots in early November, allowing JavaScript execution inside messages via the QuickJS engine. Security researcher V12 quickly demonstrated remote code execution by launching the system calculator on Android. Pavel Durov responded that no vulnerability existed because the user had to first start the bot, yet server-side fixes were deployed anyway. Multiple use-after-free and use-after-return bugs were identified in QuickJS and QuickJS-ng, some discovered with AI assistance from Claude Fable 5.1 and Mythos 5.2. Telegram isolated the widget engine into a separate process on Android, added syscall filtering, and limited nested graphical effects to prevent crashes. Desktop clients received the fixes across versions 7.4.2 and 7.4.3, while widgets were temporarily restricted server-side. Users are advised to update to Android 13.2.2 or Desktop 7.4.3 and avoid unknown bots.