Skip to main content
No exploitation reported

CVE-2026-105483

No exploitation reported by the sources we read.

  • Published2026-10-23
  • WeaknessCWE-295

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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

Timeline

dates in UTC
  1. 2026-10-2317:17CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-105483?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-105483?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2026-105483 Red Hat Product Security35 known affected

    nodejs: nodejs: TLS certificate hostname bypass via fullwidth-digit IP hostnames

    nodejs24 as a component of Red Hat Enterprise Linux 10 · nodejs24-devel as a component of Red Hat Enterprise Linux 10 · nodejs24-docs as a component of Red Hat Enterprise Linux 10 · +32 more

Full record on NVD

Fix

  1. Workaround from the vendor Red Hat Product Security CVE-2026-105483 · 35 productsTo mitigate do not pass untrusted hostnames that may contain non-ASCII or fullwidth digits into TLS clients such as tls.connect, https.request, or fetch. Restrict outbound TLS connections to trusted destinations only, and segment services that initiate TLS client connections from untrusted networks.
  2. No fix available, says the vendor Red Hat Product Security CVE-2026-105483 · 34 productsAffected
  3. No fix planned, says the vendor Red Hat Product Security CVE-2026-105483 · 1 productWill not fix

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CNACVSS 3.07.4read 2026-10-23
  • CNAweakness (CWE)CWE-295read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Published
2026-10-23
Last Modified
2026-10-23
NVD status
Received

Frequently asked questions

What is CVE-2026-105483?

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

Is CVE-2026-105483 actively exploited?

Active exploitation of CVE-2026-105483 has not been confirmed.

What is the CVSS score for CVE-2026-105483?

CVE-2026-105483 has a CVSS v3 base score of 7.4 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.

Running Node.js? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month