nodejs · Node.js · published 2026-10-23

CVE-2026-105483

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-105483 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 23% of all CVEs. This Node.js vulnerability: CVSS 7.4 (v3.0), a successful attack gives total control of the component. Fixed upstream in Node.js 26.12.1, 24.22.1, 22.23.4; Ubuntu still has unfixed releases. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Node.js 26.12.1, 24.22.1, 22.23.4.

Linux distribution packages

If you run the distro’s package rather than an upstream build, this is the version to look for.

DistroReleasePackageStatus
Debian13 trixienodejsNot affected
12 bookwormnodejsNot affected
Ubuntu26.04 LTSnodejsNo fix yet
24.04 LTSnodejsNo fix yet
Red Hat Enterprise Linux (+3 more packages)RHEL 9nodejsNot affected
RHEL 8nodejsNot affected

From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.

Patch events

  1. Patch todaySecurity release

    Language runtimeNode.js

    Node.js security releases: 26.12.1, 24.22.1, 22.23.4

    Upgrade to 26.12.124.22.122.23.4

    Why: CVE-2026-111497: Known exploited server software, total technical impact.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (24th pct)FIRST EPSS v2026.06.15
CVSS base score7.4 (v3.0)
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →