Intel

AIKIDO-2026-317410

node is vulnerable to Improper Certificate Validation

CVE-2026-106069Published Oct 21, 2026
October 21, 2026

74

CVE Score

High

Improper Certificate Validation

Are you affected? Scan for Free

TL;DR

tls.checkServerIdentity normalizes the hostname with domainToASCII and can match that form to a certificate. Spellings such as 0127.0.0.1, 0x7f.0.0.1, and 2130706433 normalize to one address while the operating system resolver connects to another. The certificate check then succeeds for a different host than the one the socket reaches. The fix rejects hostnames that net.isIP accepts only after normalization.

How do I fix this?

Upgrade the node and/or the nodejs library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and TLS connects to a non-canonical IP hostname.

Package

node

Versions

22.23.0 - 22.23.3

Fixed in 22.23.4

24.17.0 - 24.22.0

Fixed in 24.22.1

26.3.1 - 26.12.0

Fixed in 26.12.1

Background info

node is vulnerable to Improper Certificate Validation in versions 22.23.0 - 22.23.3, 24.17.0 - 24.22.0 and 26.3.1 - 26.12.0.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea