CVE-2026-105482

Node.js Addresses 10 Vulnerabilities Including High-Severity RCE Risk in Brotli Decompression

The Node.js development team disclosed ten vulnerabilities across multiple versions of the JavaScript runtime on October 21, 2026. Four of the issues received a High severity rating, with one carrying a remote code execution risk through improper handling of Brotli-compressed data. The flaw tracked as CVE-2026-111497 affects Node.js 26.x, 24.x, and 22.x branches and stems from out-of-bounds memory writes during decompression. Additional High-severity problems involve DNS name resolution truncation when NUL characters are present and hostname verification bypasses in TLS certificate validation. The project also resolved three Medium and three Low severity issues related to certificate validation, snapshot entropy reuse, and file-access permission checks. Updated releases Node.js 26.12.1, 24.22.1, and 22.23.4 incorporate fixes for both the core issues and vulnerabilities in bundled components such as c-ares, OpenSSL, SQLite, and Undici. Users of unsupported older branches are advised to migrate to currently maintained versions.

Node.js Issues Security Updates Patching Ten Vulnerabilities Including High-Severity TLS Name Verification Bypasses

The Node.js project released security updates on October 21 for release lines 26, 24, and 22, addressing ten vulnerabilities with four rated high severity. The most critical issue, CVE-2026-111497, resides in the Brotli decoder and involves an out-of-bounds write that could enable remote code execution across all three supported lines. Two additional high-severity flaws affect TLS name verification: CVE-2026-105483 bypasses checks when addresses contain full-width digits, while CVE-2026-106069 fails on imprecise IP address resolution, potentially allowing a certificate to be accepted for an unintended destination. A fourth high-severity vulnerability, CVE-2026-105482, causes the dns.resolve function to truncate names containing null characters, creating inconsistencies between queried and resolved names. Medium-severity issues include out-of-order processing in HTTP socket keep-alive, improper certificate validation for non-standard IPv4 addresses, and repeated cryptographic random values in snapshot initialization and single-executable applications affecting crypto.randomUUID and crypto.randomInt. The updates also refresh c-ares, CA certificates, Undici, OpenSSL, and SQLite, with recommendations to test HTTPS outbound connections, DNS handling, Brotli-compressed content, and permission-restricted workloads.