VulnerabilityGLOBAL

CVE-2026-105482: A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() f…

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.

Published by source
2026-10-23
First seen by Reality Radar
2026-10-23
Last verified
2026-10-23

What the official notice says

Risk: CVSS 7.4

Is this affecting you?

Add what you own or use and Reality Radar will tell you when official changes match it — with evidence and next steps.

Track it free

Sources

Evidence ledger

Every piece of evidence we store is appended to a public hash chain, so later edits are detectable. Anyone can re-verify it.

EntryKindObservedEvidence hashEntry hash
#1313new2026-10-230999919f4318…c4a28e4a3fa77bd659…ccae88

Chain head: #1479 ad3417dbc128…777bd4

Raw ledger entries (JSON) · Verify chain

Share this signal