CVE-2026-105483: CWE-295 Improper Certificate Validation in nodejs node
Description
Node.js versions 24.22.0 and 26.12.0 contain a vulnerability in TLS hostname verification where certificates without matching IP address SANs can authenticate connections to IPv4 addresses written with non-ASCII characters. This occurs because tls.checkServerIdentity() fails to recognize such hosts as IP addresses, leading to improper validation against DNS names or Common Names in certificates. This flaw is a regression from a previous fix and can allow acceptance of certificates not issued for the actual IP endpoint.
CVSS v3.0
Score 7.4high
Affected software
nodejs
node
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-105483 is a vulnerability in Node.js TLS hostname verification affecting versions 24.22.0 and 26.12.0. The issue arises when an IPv4 address is written using non-ASCII characters (e.g., fullwidth digits like `127.0.0.1`). The function tls.checkServerIdentity() does not recognize these as IP addresses and instead matches them against DNS names or Common Names in the certificate. Consequently, a certificate containing DNS entries such as `DNS:127.0.0.1` or `DNS:*.0.0.1` could be accepted for an IP endpoint it was not issued for. This vulnerability is a regression introduced after the fix for CVE-2026-48618 and is classified under CWE-295 (Improper Certificate Validation).
Potential Impact
An attacker could present a certificate with DNS names that do not correspond to the actual IP address but still be accepted by Node.js when the IP address is represented with non-ASCII characters. This improper validation can lead to man-in-the-middle attacks or unauthorized authentication, compromising confidentiality and integrity of TLS connections. The CVSS score of 7.4 (high) reflects the potential for significant impact on confidentiality and integrity without requiring user interaction or privileges.
Mitigation Recommendations
The vulnerability affects specific Node.js versions 24.22.0 and 26.12.0. Since no patch links or vendor advisory content are provided, patch status is not yet confirmed — check the official Node.js security advisories for updates and remediation guidance. Until a fix is available, avoid using these specific Node.js versions or avoid connecting to hosts using non-ASCII character representations of IP addresses. Monitor vendor channels for official patches or updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2026-10-05T15:00:00.729Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 6adb8965d73cc49347a5c6e5
Added to database: 10/23/2026, 16:20:53 UTC
Last enriched: 10/23/2026, 16:35:14 UTC
Last updated: 10/23/2026, 16:35:52 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.