CVE-2026-105482: 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.
Overview
- Severity
- High (CVSS 7.4)
- CVSS Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Exploit Status
- Not Exploited
- Patch Tuesday
- 2026-Oct
- Released
- 2026-10-25
- Last Updated
- 2026-10-26
- EPSS Score
- 0.42% (percentile: 36.4%)
Detection & Weaponization (1 sources)
Maturity: Exploit
- GitHub PoC: 2 repositories
Affected Products (1)
Open Source Software
- azl3 nodejs 24.21.0-1 on Azure Linux 3.0
Revision History
- 2026-10-25: Information published.
- 2026-10-26: Information published.