CVE-2026-106072 Affecting nodejs-packaging package, versions <0:2021.06-6.module+el9.7.0+40153+4d595597


Severity

Recommended
high

Based on Rocky Linux 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-ROCKY9-NODEJSPACKAGING-22099249
  • published31 Oct 2026
  • disclosed23 Oct 2026

Introduced: 23 Oct 2026

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

How to fix?

Upgrade Rocky-Linux:9 nodejs-packaging to version 0:2021.06-6.module+el9.7.0+40153+4d595597 or higher.
This issue was patched in RLSA-2026:92378.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs-packaging package and not the nodejs-packaging package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:9 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