CVE-2026-106069 Affecting nodejs-26 package, versions <26.12.1-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.28% (20th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-NODEJS26-21723702
  • published27 Oct 2026
  • disclosed23 Oct 2026

Introduced: 23 Oct 2026

NewCVE-2026-106069  (opens in a new tab)

How to fix?

Upgrade Chainguard nodejs-26 to version 26.12.1-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs-26 package and not the nodejs-26 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1