# CVE-2026-106069: CVE-2026-106069

Status: published. Published: 2026-10-23. Updated: 2026-11-02.

A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`.

`tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address.

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

## Remediation

No remediation reported in collected sources

## Affected products and versions

- nodejs / node: ≥ 22.23.3; ≤ 22.23.3 (affected, semver); ≥ 24.22.0; ≤ 24.22.0 (affected, semver); ≥ 26.12.0; ≤ 26.12.0 (affected, semver). Source: CNA: hackerone

## Severity and prioritization

- CVSS 3.0: 7.4 (high); CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N; source: CNA: hackerone

- CISA KEV: No listing in collected sources

- EPSS: 0.30% as of 2026-11-01; percentile 23.24%

- SSVC: exploitation none; automatable no; technical impact total; source ADP: CISA-ADP

- Weaknesses: CWE-295

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://nodejs.org/en/blog/vulnerability/october-2026-security-releases (CNA: hackerone)

## Provenance

- CNA: hackerone: https://www.cve.org/CVERecord?id=CVE-2026-106069; retrieved 2026-11-02; source updated 2026-11-02

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-106069; retrieved 2026-11-02; source updated Not reported

Revision: b7d90c4e1aa149b2e06eb55ec904bd5676347c3d4ba362e543bd860b3c2dcec9

Canonical: https://y2.dev/cve/CVE-2026-106069

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.