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().
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-105482?
CVE-2026-105482 is a high-severity vulnerability in nodejs node, published on 23 Oct 2026.
Official description
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.
Weakness: CWE-284
Which versions are affected by CVE-2026-105482?
2 open source packages ship an affected version, including node and node-min.
| Package | Affected | Fixed in |
|---|---|---|
node Bitnami | All versions | 22.23.4, 24.22.1, 26.12.1 |
node-min Bitnami | All versions | 22.23.4, 24.22.1, 26.12.1 |
How do I fix CVE-2026-105482?
Upgrade node to a fixed version for your release line: 22.23.4, 24.22.1 or 26.12.1.
Is CVE-2026-105482 being exploited?
There is no known exploitation of CVE-2026-105482 in the wild and no public exploit code.
Public exploit code: 3 proofs of concept on GitHub.
Sources
Also known as ALPINE-CVE-2026-105482, AZL-111035, BIT-node-2026-105482, BIT-node-min-2026-105482, DEBIAN-CVE-2026-105482, GHSA-4qmx-59c6-fr6r and 1 more.