Vulnerability in nodejs node

[ Description ]Official description

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.

[ Fixes ]Fixes and patches

No fix or interim patch is linked from our sources yet. Check the vendor references below and limit exposure of affected systems until a fix is available.

[ Advisories ]Government CERT advisories

• BSI CERT-Bund21 Oct 2026WID-SEC-2026-4117

  Node.js: Multiple vulnerabilities Translated from German

  Risk mediumCVE-2026-106070CVE-2026-106069CVE-2026-105483+7 more CVEs

[ References ]References

• nodejs.org/en/blog/vulnerability/october-2026-security-releases