Multiple High-Severity Vulnerabilities Affecting Node.js (TLS, DNS, and Brotli Decompression)
Node.js has officially released security updates across all active release branches (26.x, 24.x, and 22.x) to address ten security vulnerabilities, including four high-severity flaws. The most critical risk stems from an out-of-bounds write flaw in the Brotli decompression engine that can lead to remote code execution (RCE) when handling untrusted compressed payloads. Additional vulnerabilities enable TLS certificate hostname verification bypasses, DNS lookup name truncation,...
Description
Technical context and vulnerability details
Node.js is an open-source, cross-platform JavaScript runtime environment commonly used to build scalable network applications, web servers, microservices, and backend APIs across corporate environments.
The released security maintenance updates resolve ten vulnerabilities across the runtime and its embedded core libraries:
- CVE-2026-111497 (High): An out-of-bounds memory write vulnerability in the Brotli decompression module affecting Node.js 26.x, 24.x, and 22.x. An attacker supplying crafted Brotli-compressed data can cause memory corruption, potentially leading to arbitrary remote code execution or application crash.
- CVE-2026-105483 (High): TLS certificate hostname verification bypass when an IP address contains full-width digits, affecting Node.js 26.x and 24.x release branches.
- CVE-2026-106069 (High): TLS hostname validation flaw involving hostnames that loosely resolve to an IP address, impacting all supported branches (26.x, 24.x, 22.x) and allowing man-in-the-middle spoofing.
- CVE-2026-105482 (High): The
dns.resolvefunction truncates domain names containing a NUL character, leading to name resolution inconsistencies and security check bypasses across all branches. - CVE-2026-105481 (Medium): HTTP connection handling flaw where a keep-alive socket can process a response written before its corresponding request was transmitted.
- CVE-2026-106072 (Medium): Improper certificate validation for non-standard IPv4 hostnames allowing DNS certificate names to authenticate arbitrary IP endpoints.
- CVE-2026-106074 (Medium): Entropy repetition flaw in cached random data within startup snapshots and single executable applications (SEA), causing repeated values from
crypto.randomUUID()andcrypto.randomInt(). - CVE-2026-106070 (Low): Attacker-controlled bytes returned following failed ZIP archive header checks in Node.js 26.x.
- CVE-2026-106071 (Low): Excessive filesystem access granted through wildcard pattern matching under the experimental Permission Model in Node.js 26.x.
- CVE-2026-106073 (Low): Permission Model restriction bypass via
fs.realpathSyncacross all supported release lines.
These updates also include patched versions of embedded third-party dependencies, including OpenSSL, c-ares, Undici, SQLite, and updated trusted root CA certificates.
Potential Risks & Impact
Potential consequences upon exploitation
- Remote arbitrary code execution via crafted Brotli compressed data;
- Bypass of TLS certificate verification and hostname validation;
- Man-in-the-Middle (MitM) attacks against outbound HTTPS connections;
- Domain spoofing and inconsistency in DNS lookups;
- Cryptographic predictability due to repeated pseudo-random number generator (PRNG) output;
- Unauthorized file system access and permission model bypass;
- Denial of service (DoS) and application instability.
Affected systems
Products, components and targeted versions
- Node.js 26.x: versions prior to 26.12.1;
- Node.js 24.x: versions prior to 24.22.1;
- Node.js 22.x (LTS): versions prior to 22.23.4;
- All end-of-life (EOL) Node.js release branches (such as 20.x, 18.x, and earlier) which no longer receive security maintenance patches.
Recommended Remediations & Actions
Immediate actions and recommended mitigations
- Immediately upgrade Node.js runtimes to the latest patched releases: version 26.12.1, 24.22.1, or 22.23.4 depending on the deployed branch;
- Rebuild and redeploy application container images, serverless functions, and local runtime dependencies incorporating the patched releases;
- Restart all backend services, daemons, and microservices relying on Node.js;
- Pay particular attention to applications decompressing untrusted Brotli input or establishing outbound TLS connections to external endpoints;
- Migrate any remaining systems on end-of-life branches (Node.js <= 20.x) to an actively supported LTS branch (Node.js 22.x or 24.x).
Sources & External Links
Vendor security advisories and documentation
- https://nodejs.org/en/blog/vulnerability/october-2026-security-releases
- https://cybersecuritynews.com/node-js-releases-security-updates/
- https://nvd.nist.gov/vuln/detail/CVE-2026-111497
- https://nvd.nist.gov/vuln/detail/CVE-2026-105483
- https://nvd.nist.gov/vuln/detail/CVE-2026-106069
- https://nvd.nist.gov/vuln/detail/CVE-2026-105482
Advisory Specifications
CSIRT Emergency Response
Is your organization affected or do you suspect an incident? Our security experts are available to assist.
Report an incidentGet our alerts by email
Subscribe to receive our security alert bulletins and Iservices news straight to your inbox.