Improper Validation of Certificate with Host Mismatch Affecting nodejs24-full-i18n package, versions <1:24.22.1-3.hum1


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

Social Trends
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-RHEL10-NODEJS24FULLI18N-21857635
  • published30 Oct 2026
  • disclosed21 Oct 2026

Introduced: 21 Oct 2026

NewCVE-2026-105483  (opens in a new tab)
CWE-297  (opens in a new tab)

How to fix?

Upgrade RHEL:10 nodejs24-full-i18n to version 1:24.22.1-3.hum1 or higher.
This issue was patched in RHSA-2026:89206.

NVD Description

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

A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (127.0.0.1).

tls.checkServerIdentity() did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing DNS:127.0.0.1 or DNS:*.0.0.1 could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.

This vulnerability affects Node.js 26.x and 24.x.

CVSS Base Scores

version 3.1