Nodejs node
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 22.23.3, <= 22.23.3
- >= 24.22.0, <= 24.22.0
- >= 26.12.0, <= 26.12.0
Mitigation
The record names no fix. Check the vendor advisory below.
Timeline
Days relative to CVE publicationFirst public PoC 2 days before publication; not in CISA KEV. First PoC: CaterMaoZi/CVE-2026-105482-POC (created 21 Oct 2026, found by us: 14 Nov 2026).
PoC repositories
Found on GitHub.4 PoCs
PoCs 4
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| CaterMaoZi/CVE-2026-105482-POC | 21 Oct 2026 −2 d | 14 Nov 2026 | 9 | PoC |
| CompleTech-Security/node-cve-2026-105482-check | 23 Oct 2026 +8 h | 14 Nov 2026 | 0 | Scanner
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
| completetech-security/node-cve-2026-105482-check | 23 Oct 2026 +8 h | 14 Nov 2026 | 0 | Scanner
Flags · score 30
Below the suspicion threshold (50); does not change the assessment. |
| EthanTech-Offical/CVE-2026-105482-Reproduce | 28 Oct 2026 +4.4 d | 14 Nov 2026 | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.