Improper Certificate Validation Affecting nodejs24-libs package, versions <1:24.22.1-1.amzn2023.0.1


Severity

Recommended
high

Based on Amazon Linux security rating.

Threat Intelligence

EPSS
0.55% (46th 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-AMZN2023-NODEJS24LIBS-21706650
  • published25 Oct 2026
  • disclosed23 Oct 2026

Introduced: 23 Oct 2026

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

How to fix?

Upgrade Amazon-Linux:2023 nodejs24-libs to version 1:24.22.1-1.amzn2023.0.1 or higher.
This issue was patched in ALAS2023-2026-3330.

NVD Description

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