Linux · Rocky Linux · Security advisory · November 11, 2026

RLSA-2026:96088: nodejs24 security update

RLSA-2026:96088, released November 11, 2026, fixes 9 CVEs in nodejs24 (version 1:24.22.1-3.el10_2). None of them is reported as exploited. Patch Radar priority: High.

High
CVEs closed
9
None rated Critical
Exploited
0
None reported
Highest CVSS
9.1
Base score, 0 to 10
Highest EPSS
0.0049
42nd percentile

Priority of the 9 CVEs

Patch now 0 Urgent 0 High 9 Routine 0

Fixed package versions

ProductReleaseFixed in
nodejs24rocky 101:24.22.1-3.el10_2

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
High CVE-2026-102278 brace-expansion: DoS via uncontrolled recursion on nested brace groups causing stack exhaustion8.1 0.0049 None reported
High CVE-2026-105482 A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse(). This is an incomplete fix of CVE-2026-48930, which only covered dns.lookup() and the net/tls host options. Because the name is passed to c-ares as a C string, resolving attacker.example\0.trusted.example queries attacker.example and returns its records without any error. Applications that validate a hostname, for example against a domain allowlist, and then resolve it with dns.resolve*() can act on records for a different name than the one they validated. This vulnerability affects Node.js 26.x, 24.x, and 22.x.8.1 0.0047 None reported
High CVE-2026-102276 brace-expansion: DoS via uncontrolled recursion in parseCommaParts causing stack exhaustion8.1 0.0046 None reported
High CVE-2026-109869 nodejs: ELSA-2026-96226: nodejs:24 security update (IMPORTANT)7.5 0.0034 None reported
High CVE-2026-105483 A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`１２７.0.0.1`). `tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618. This vulnerability affects Node.js **26.x** and **24.x**.8.1 0.0030 None reported
High CVE-2026-106069 A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`. `tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.8.1 0.0030 None reported
High CVE-2026-87018 nodejs: ELSA-2026-96226: nodejs:24 security update (IMPORTANT)7.5 0.0019 None reported
High CVE-2026-109383 nodejs: ELSA-2026-96226: nodejs:24 security update (IMPORTANT)9.1 0.0018 None reported
High CVE-2026-109829 nodejs24: undici is an HTTP client library for Node.js9.1 0.0015 None reported
Showing 1 to 9 of 9 1

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.