Node.js DNS resolution NUL byte truncation in dns.resolve*()
CVE-2026-105482High
Node.js DNS resolution functions dns.resolve*() and dns.reverse() silently truncate hostnames containing a NUL byte character, treating them as C strings. An attacker can craft a hostname like attacker.example\0.trusted.example to make the function resolve only attacker.example and return its records without error. Applications that validate hostnames against an allowlist before resolving them can be tricked into acting on DNS records for a different domain than the one they checked.
Plain English summary of the NVD and CISA text, checked by machine against both.
Scores and dates
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Detail
Reports naming this CVE5 in total
· Cisco Security Advisory
Vulnerabilities in Node.js and Brotli Affecting Cisco Products: October 2026 (opens in a new tab)· Cisco Security Advisory
Vulnerabilities in Node.js Affecting Cisco Products: October 2026 (opens in a new tab)· Qualys Security Blog
Waiting on a Node.js Upgrade? Build a Stopgap with the Controls You Own (opens in a new tab)· Cisco Security Advisory
Vulnerabilities in node.js Affecting Cisco Products: October 2026 (opens in a new tab)· FortiGuard Labs IR Advisories
Multiple Node.js CVEs (opens in a new tab)