CVE Intelligence
High Cryptography

CVE-2026-105483 — A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address...

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 (`１２７.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**.

Published Oct 23, 2026 · Updated Oct 23, 2026 · Sources: CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: hackerone

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.3%
ahead of 23% of scored CVEs · Oct 30, 2026
Affects
Nodejs
Node
CVSS base
7.4
High · 3 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Nodejs Node).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Nodejs Node ≥ 24.22.0 and ≤ 24.22.0≥ 26.12.0 and ≤ 26.12.0 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.4 CVSS 3.0 High 2.2 5.2 support@hackerone.com via NIST National Vulnerability Database
7.4 CVSS 3.0 High — — GitHub, Inc. via GitHub Security Advisories
7.4 CVSS 3.0 High — — hackerone via CVE Program (cve.org) e CISA ADP
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (score shown at the top: support@hackerone.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-295 · Improper Certificate Validation

Other CVEs with this weakness →

EPSS over time FIRST

Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.30%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Check TLS negotiations and unexpected certificates in the component’s traffic.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Published → Awaiting Analysis
    Oct 23, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 23, 2026
  • CVSS changed · 7.4
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • Record created in this database
    Oct 23, 2026 · CVE Program (cve.org) e CISA ADP
  • CVE published
    Oct 23, 2026 · hackerone

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 23, 2026 – Oct 23, 2026
  • 1× Official description updated · Oct 23, 2026 – Oct 23, 2026

References

3 on the record

Elsewhere on this site

Nodejs
every CVE for this vendor
Cryptography
same class
CWE-295
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-106074 Use of Insufficiently Random Values in Nodejs Node 7d
  • CVE-2026-106071 Improper Access Control in Nodejs Node 7d
  • CVE-2026-106072 Improper Certificate Validation in Nodejs Node 7d
  • CVE-2026-106073 Improper Access Control in Nodejs Node 7d
  • CVE-2026-106070 A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong… 7d
  • CVE-2026-105482 Improper Access Control in Nodejs Node 7d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-105483 is "A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address...", rated High. It affects Node (Nodejs); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.4 describes technical severity. EPSS 0.30% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.