Aller au contenu
en Se connecter
7.7 Élevée

CVE-2026-48618 A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls…

Description

A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

Produits et versions touchés

Produit Versions touchées Corrigé en
Node 26.3.0 Pas de correctif indiqué
Node 24.16.0 Pas de correctif indiqué
Node 22.22.3 Pas de correctif indiqué
Red Hat Enterprise Linux 10 Versions non publiées
Red Hat Enterprise Linux 10.0 Extended Update Support Versions non publiées
Red Hat Enterprise Linux 9 9080020260626075442 premières → < 9080020260626075442.rhel9 9080020260626075442.rhel9
Red Hat Hardened Images 20.20 premières → < 20.20.2-1.hum1 20.20.2-1.hum1
Red Hat Enterprise Linux 8 8100020260703140402.6 premières → < 8100020260703140402.6d880403 8100020260703140402.6d880403

Références

Chronologie

  1. Publiée
  2. Dernière modification

Autres CVE de Node

Les 129 CVE de Node →
CVE-2026-105482 A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*()… 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 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-106074 A flaw in Node.js `crypto` causes the internal entropy caches used by `crypto.randomUUID()`, `crypto.randomUUIDv7()`,… 4.8 Moyenne
Suivre cette CVE