Node.js Fixes High-Severity Brotli Decoder Flaw Leading to Remote Code Execution

A high-severity vulnerability in the bundled Brotli decoder of Node.js allows out-of-bounds writes when processing attacker-controlled compressed data, potentially resulting in remote code execution. The flaw, tracked as CVE-2026-111497, affects all supported branches including 22.x, 24.x, and 26.x prior to the October 21, 2026 security release. Patched versions 22.23.4, 24.22.1, and 26.12.1 address the memory corruption issue that arises during Brotli decompression in services accepting third-party content. The same update resolves additional high-severity problems, notably hostname validation weaknesses in TLS. Organizations using unsupported branches such as 18.x, 20.x, 23.x, and 25.x must migrate to maintained releases, while those linking against system Brotli libraries should verify inclusion of upstream commit 0ed4268. Security teams are advised to audit all environments, including containers and CI pipelines, that process Brotli-encoded data.

HispasecTranslated from Spanish

Read at source

Node.js has released critical security updates addressing a high-severity flaw in its bundled Brotli decoder that can lead to out-of-bounds memory writes and remote code execution.

The vulnerability, identified as CVE-2026-111497, occurs when a Node.js process decodes attacker-controlled Brotli content, a scenario common in services that accept compressed responses or handle third-party data. This memory corruption issue falls into the category of out-of-bounds writes, where the process writes data beyond allocated buffers, potentially allowing arbitrary code execution under favorable conditions.

The October 21, 2026 security release provides fixes for all currently supported branches. Updated versions include Node.js 22.23.4, 24.22.1, and 26.12.1. Branches 18.x, 20.x, 23.x, and 25.x receive no official patches and require migration to a supported release.

Environments that compile Node.js against a system-provided Brotli library must ensure the dependency incorporates upstream commit 0ed4268 to eliminate residual risk. The same patch batch resolves additional high-severity issues, including hostname validation problems in TLS implementations.

Organizations should inventory services that decode Brotli data, prioritize those accepting untrusted input, and apply updates across production systems, container images, CI runners, and developer workstations to prevent reintroduction of the vulnerability.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Vulnerabilities & Exploits

Telegram for Android Patches Voice Call Vulnerability Enabling Code Execution
Yandex Patches Millions of Stations After eMudhra Certificate Keys Compromised
Cisco ASA and FTD Face DoS Vulnerability in SSL VPN Already Exploited in the Wild