CVE-2026-105482
Node.js: dns.resolve truncates hostnames containing a NUL character
Technology
Node.js
CVSS Score
7.4 / 10.0
Affected Versions
>=22.0.0 <22.23.4; >=24.0.0 <24.22.1; >=26.0.0 <26.12.1
Upstream Fix
22.23.4; 24.22.1; 26.12.1
Published
October 23, 2026
OSSeva Coverage
Fixed upstream
Description
The dns.resolve*() functions and dns.reverse() silently truncate a hostname at a NUL byte, 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 an error, so an application that validates a hostname against an allowlist and then resolves it can act on records for a different name. An incomplete fix of CVE-2026-48930, which covered only dns.lookup(). Rated High by Node.js; the score is the CNA's, as NVD had not yet analysed the record. Fixed in 22.23.4, 24.22.1 and 26.12.1.
Is your Node.js deployment affected?
If you're running >=22.0.0 <22.23.4; >=24.0.0 <24.22.1; >=26.0.0 <26.12.1, you need this patch. Book a discovery call to get covered.
Get a quote
Running Node.js >=22.0.0 <22.23.4; >=24.0.0 <24.22.1; >=26.0.0 <26.12.1?
Send your work email and a senior engineer will tell you whether this CVE applies to your versions and who patches it. Reply within 1 business day.
Prefer to talk or read more first?