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.
Fix
Microsoft's update · Important
- Release Notes — azl3 nodejs 24.21.0-1 on Azure Linux 3.0 · build 24.22.1-0
From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-28.
Public exploits 4
- CaterMaoZi/CVE-2026-105482-POC PoC on GitHub
- CompleTetech-Security/node-cve-2026-105482-check PoC on GitHub
- EthanTech-Offical/CVE-2026-105482-Reproduce PoC on GitHub
- completetech-security/node-cve-2026-105482-check PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Vendor advisories in the News 1
- Node2Shell CVEs Fortinet PSIRT Advisories · 2026-10-26
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 4
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-23 16:15
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-23 19:42
- StatusReceived → PublishedNVD modified 2026-10-23 16:15
- First seenCVSS 7.4NVD modified 2026-10-23 17:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.