vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-106069

HIGH
7.4
CVSS Score
Published: October 23, 2026 at 04:15 PM UTC
Updated: October 23, 2026 at 07:42 PM UTC
1 product affected across 1 vendorNode.js

Using node by nodejs?

Get instant alerts when new vulnerabilities affect node - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH7.4
Exploit prediction
EPSS 0.3%

Description

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Node.js· Node.js
90%
22.23.324.22.026.12.0

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

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

CVSS

7.4HIGHhackerone
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-295

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card