Skip to main content
Public proof of concept

CVE-2026-105482

A public proof of concept exists; no exploitation attested.

  • Published2026-10-23
  • WeaknessCWE-284

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-10-2317:17CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-105482?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-105482?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2026-105482 Red Hat Product Security61 known affected

    nodejs: nodejs: dns.resolve truncates hostnames containing a NUL character

    nodejs as a component of Red Hat Enterprise Linux 10 · nodejs-devel as a component of Red Hat Enterprise Linux 10 · nodejs-docs as a component of Red Hat Enterprise Linux 10 · +58 more

Full record on NVD

Fix

  1. Workaround from the vendor Red Hat Product Security CVE-2026-105482 · 61 productsTo mitigate, do not pass untrusted strings into dns.resolve; reject hostnames that contain embedded NUL bytes before DNS resolution. Limit which components may perform DNS lookups on attacker-influenced names, and restrict network reachability of those services.
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-105482 · 61 productsAffected

Detection

read 2026-10-23 19:24 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedCaterMaoZi/CVE-2026-105482-POC
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CNACVSS 3.07.4read 2026-10-23
  • CNAweakness (CWE)CWE-284read 2026-10-23
  • PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Published
2026-10-23
Last Modified
2026-10-23
NVD status
Received

Frequently asked questions

What is 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.

Is CVE-2026-105482 actively exploited?

Active exploitation of CVE-2026-105482 has not been confirmed.

What is the CVSS score for CVE-2026-105482?

CVE-2026-105482 has a CVSS v3 base score of 7.4 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.

Running Node.js? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database