CVE-2026-105482

A flaw was found in the Node.js DNS resolver APIs. Hostnames passed to dns.resolve that contain an embedded NUL character can be truncated when processed by c-ares. An attacker who can supply such a name may cause the application to resolve and act on an unintended hostname. Mitigation To mitigat...

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 strin...

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 strin...

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 strin...

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 strin...

CVE-2026-105482

A flaw in the Node.js DNS resolution mechanism allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and dns.reverse(). Because names are passed to c-ares as C strings, an attacker could use a hostname like attacker.example .trusted.example to bypass vali...

EUVD-2026-109105

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 strin...

Vaadin and the October 2026 Node.js security releases

A deployed Vaadin application does not run Node.js, so it is not exposed to the vulnerabilities fixed in the Node.js security releases of 21 October 2026. Vaadin uses Node.js only to build the frontend and to run development mode, which means the exposure, where there is any, is in build and...

Node.js 22.x < 22.23.4 / 24.x < 24.22.1 / 26.x < 26.12.1 Multiple Vulnerabilities

The version of Node.js installed on the remote host is 22.x prior to 22.23.4, 24.x prior to 24.22.1, or 26.x prior to 26.12.1. It is, therefore, affected by multiple vulnerabilities as referenced in the Wednesday, October 21, 2026 Security Releases advisory. - An out-of-bounds write in the Brotli...

Node.js < 22.23.4, < 24.22.1, < 26.12.1 - Improper Null Termination in dns.resolve() leading to Hostname Spoofing

Improper Null Termination in dns.resolve leading to Hostname Spoofing vulnerability discovered by hasanfleyah in WordPress npm Node.js versions 22.23.4...

Exploit for CVE-2026-105482

CVE-2026-105482 – Node.js dns.resolve NUL byte truncation...

CVE-2026-105482

Node.js dns.resolve and the dns promises resolver accept names containing NUL characters and pass them to c-ares as C strings, so the queried name is silently truncated at the NUL byte. Fixed in 22.23.4, 24.22.1 and 26.12.1...

Node.js: dns.resolve truncates names containing NUL char

A patch for CVE-2026-48930 was found to be incomplete. The fix rejected embedded NUL bytes in DNS lookup entry points but failed to apply the same validation to dns.resolve entry points that interface with c-ares binding. When a NUL character was passed within a hostname to dns.resolve4, the call...