Aller au contenu
en Se connecter
7.4 Élevée

CVE-2026-105482 A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*()…

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.

Produits et versions touchés

Produit Versions touchées Corrigé en
Node 26.12.0 Pas de correctif indiqué
Node 24.22.0 Pas de correctif indiqué
Node 22.23.3 Pas de correctif indiqué

Références

Chronologie

  1. Publiée
  2. Dernière modification

Autres CVE de Node

Les 129 CVE de Node →
CVE-2026-106071 A flaw in Node.js Permission Model filesystem enforcement can grant access to paths that do not match a wildcard… 3.6 Faible CVE-2026-106070 A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after… 3.7 Faible CVE-2026-105483 A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a… 7.4 Élevée CVE-2026-106069 A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP… 7.4 Élevée
Suivre cette CVE