nday
CVE-2026-105483

Node.js: cryptographic failureTitle composed by nday; the CVE record has none.

nodejs / node

Technical analysis appeared 1 day before the CVE record was published. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

cryptographic failure
CWE-295, stated by the CNA hackerone and NVD, republishing [email protected]
remote, unauthenticated
AV:N, PR:N, UI:N in CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (CVSS 3.0) from the CNA hackerone
network
AV:N in CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (CVSS 3.0) from the CNA hackerone
no authentication required
PR:N in CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (CVSS 3.0) from the CNA hackerone
no user interaction
UI:N in CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (CVSS 3.0) from the CNA hackerone
Node.js
affected products in the CVE record: nodejs · node
open-source library / framework
affected products in the CVE record: nodejs · nodethe product type of Node.js in nday's product registry
stage
ANA
disclosed
cvss
7.4 HIGH v3.0

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
10-23T16:15Z
PATpatch
no record yet
ANAanalysis
10-22T18:45Z
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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**.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:H
High: success depends on conditions outside the attacker's control, such as gathering details of the target or winning a race
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

CVSS 3.0 vector from the CVE record, scored by the CNA hackerone.

Event log

+ANAtechnical analysis

Reply on the oss-security mailing list: “Re: Upcoming Node.js security release 2026/10/21”.

src osssec 2026/q4/310 · nday , observed live · raw
{
  "id": 495800,
  "type": "analysis_published",
  "source": "osssec",
  "url": "https://seclists.org/oss-sec/2026/q4/310",
  "occurred_at": "2026-10-22T18:45:44Z",
  "observed_at": "2026-11-20T08:13:28.642196Z",
  "is_backfill": false,
  "dedupe_key": "2026/q4/310",
  "detail": {
    "list": "oss-security",
    "author": "Alan Coopersmith",
    "subject": "Re: Upcoming Node.js security release 2026/10/21",
    "is_reply": true
  }
}
+DISdisclosed

CVE record published by hackerone. CVSS 7.4, high.

src cvelist · nday , bulk import · raw
{
  "id": 461553,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-105483",
  "occurred_at": "2026-10-23T16:15:05.773Z",
  "observed_at": "2026-11-13T05:40:23.74225Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
      "version": "3.0",
      "base_score": 7.4,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2026-11-02T15:34:42.524980Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-10-23T16:15:05.773Z",
    "assigner_short_name": "hackerone"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.