CVE-2026-105482

Vulnerability record

  • High 7.4

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.

Key facts

Published
23 Oct 2026
Last changed
2 Nov 2026
Assigned by
hackerone
EPSS
0.468% likely to be exploited in the next 30 days, higher than 41.098% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.4CVSS 3.0, Highfrom the CNA (hackerone)CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
nodejsnode
  • Default status: unaffected
  • 22.23.3 up to and including 22.23.3 (affected)
  • 24.22.0 up to and including 24.22.0 (affected)
  • 26.12.0 up to and including 26.12.0 (affected)

Timeline

  1. 23 Oct 2026 Published

Weakness

References