CVE-2026-106072 Affecting nodejs24 package, versions <24.22.1-150700.15.21.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.62% (50th 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-SLES157-NODEJS24-22192806
  • published4 Nov 2026
  • disclosed2 Nov 2026

Introduced: 2 Nov 2026

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

How to fix?

Upgrade SLES:15.7 nodejs24 to version 24.22.1-150700.15.21.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs24 package and not the nodejs24 package as distributed by SLES. See How to fix? for SLES:15.7 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1