CVE-2026-106069 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.3% (24th 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-22099190
  • published31 Oct 2026
  • disclosed23 Oct 2026

Introduced: 23 Oct 2026

NewCVE-2026-106069  (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 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