ZDF
Sign inSign up

Vulnerabilities

Vulnerability · 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().

Published Oct 22, 2026 · catalog updated Oct 24, 2026 · A flaw in Node.js

Last checked Oct 31, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-105482. EPSS is 0.47%. Act only if a listed version of A flaw in Node.js is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (A flaw in Node.js).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.47%
Remediation
Advisory link
Affected products
Alpine:v3.21 nodejs · Alpine:v3.22 nodejs · Alpine:v3.23 nodejs · Alpine:v3.24 nodejs · Debian:12 nodejs · Debian:13 nodejs

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Alpine:v3.21 nodejs0 → 22.23.4-r0
  • Alpine:v3.22 nodejs0 → 22.23.4-r0
  • Alpine:v3.23 nodejs0 → 24.22.1-r0
  • Alpine:v3.24 nodejs0 → 24.22.1-r0
  • Debian:12 nodejs18.13.0+dfsg1-1, 18.13.0+dfsg1-1.1, 18.19.0+dfsg-1
  • Debian:13 nodejs20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2
  • Debian:14 nodejs20.19.2+dfsg-1, 20.19.4+dfsg-1, 20.19.5+dfsg+~cs20.19.12-1

How to fix CVE-2026-105482

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-105482. EPSS is 0.47%. Act only if a listed version of A flaw in Node.js is installed.

Which versions are affected?

Compare what you have installed with 0 → 22.23.4-r0, 0 → 24.22.1-r0, 18.13.0+dfsg1-1, 18.13.0+dfsg1-1.1, 18.19.0+dfsg-1, 20.19.2+dfsg-1, 20.19.2+dfsg-1+deb13u1, 20.19.2+dfsg-1+deb13u2, 20.19.2+dfsg-1, 20.19.4+dfsg-1, 20.19.5+dfsg+~cs20.19.12-1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.47%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Cisco securityDebian security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 22, 2026 · Trivy Vulnerability DB

    Detected

  2. Oct 22, 2026 · Trivy Vulnerability DB

    Updated

    The description or metadata changed.

  3. Oct 24, 2026 · Trivy Vulnerability DB

    Fix available

    nodejs fixed in 22.23.4-r0; nodejs fixed in 22.23.4-r0; nodejs fixed in 24.22.1-r0; nodejs fixed in 24.22.1-r0

  4. Oct 24, 2026 · Trivy Vulnerability DB

    Fix available

    nodejs fixed in 22.23.4-r0

  5. Oct 24, 2026 · Trivy Vulnerability DB

    Fix available

    nodejs fixed in 24.22.1-r0

  6. Oct 24, 2026 · Trivy Vulnerability DB

    Updated

    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

Sources

  • BSI CERT-BundGovernment advisoryCVE-2026-105482

    Node.js: Mehrere Schwachstellen

    wid.cert-bund.de
  • Cisco Security AdvisoriesVendor advisoryCVE-2026-105482

    On October 21, 2026, Node.js announced the availability of fixes for multiple vulnerabilities across the following supported release lines: 22.x, 24.x, and 26.x. These vulnerabilities impact critical operations such as the Brotli decoder, DNS resolution, and TLS certificate valid

    sec.cloudapps.cisco.com
  • CVE.orgVulnerability recordCVE-2026-105482

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-105482

    30-day exploitation probability 0.47%

    first.org
  • Trivy Vulnerability DBPackage advisoryALPINE-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 passe

    osv.dev
  • Trivy Vulnerability DBPackage advisoryDEBIAN-CVE-2026-105482
    osv.dev
  • urlscan.ioThreat intelligenceCVE-2026-105482
    urlscan.io

References

Freshness

Last verified in this catalog Oct 29, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • urlscan.ioOct 31, 2026
  • Cisco Security AdvisoriesOct 31, 2026
  • BSI CERT-BundOct 31, 2026
  • FIRST EPSSOct 29, 2026
  • Trivy Vulnerability DBOct 25, 2026
  • CVE.orgOct 23, 2026
  • Trivy Vulnerability DBOct 23, 2026