CVE-2026-106072

State
Published
Severity
6.7 Medium
Published
Oct 23, 2026
Updated
Oct 23, 2026
Reserved
Oct 6, 2026

Read the record on cve.org

Description

A flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client connects using a non-canonical IPv4 spelling, such as `0177.0.0.1`, `0x7f.0.0.1`, `2130706433` or `127.1`.

`tls.checkServerIdentity()` did not classify these hosts as IP addresses, but normalized them to their canonical form and matched the result against the certificate DNS names. A certificate containing `DNS:127.0.0.1` and no `IP Address:127.0.0.1` SAN was therefore accepted, while the same certificate is correctly rejected for `127.0.0.1`. Exploitation requires a certificate with a numeric DNS SAN issued by a CA trusted by the client, and a platform resolver that accepts these spellings, such as glibc.

This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

Scores

CVSSScoreVectorSource
3.06.7 MediumCVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:Lhackerone

Weaknesses

  • CWE-295 Improper Certificate Validation

Affected Products

ProductVersions
nodenodejs
  • 22.23.3 through 22.23.3Affected
  • 24.22.0 through 24.22.0Affected
  • 26.12.0 through 26.12.0Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.