CVE-2026-106069

CVE Details

Release Date:2026-10-23
Impact:Important What is this?

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

See more information about CVE-2026-106069 from MITRE CVE dictionary and NIST NVD


NOTE: The following CVSS metrics and score provided are preliminary and subject to review.


CVSS v3 metrics

Base Score: 7.4
Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Version: 3.1
Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality Impact: High
Integrity Impact: High
Availability Impact: None

Errata information


PlatformErrataRelease Date
Oracle Linux version 8 (nodejs) ELSA-2026-923762026-10-30
Oracle Linux version 8 (nodejs-nodemon) ELSA-2026-923762026-10-30
Oracle Linux version 8 (nodejs-packaging) ELSA-2026-923762026-10-30
Oracle Linux version 9 (nodejs) ELSA-2026-923782026-10-30
Oracle Linux version 9 (nodejs-nodemon) ELSA-2026-923782026-10-30
Oracle Linux version 9 (nodejs-packaging) ELSA-2026-923782026-10-30


This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections:

software.hardware.complete