nodejs · Node.js · published 2026-06-26

CVE-2026-48618

This month EPSS 3.1% with high severity (CVSS 7.7).

CVE-2026-48618 is not known to be exploited in the wild. EPSS estimates a 3.1% chance of exploitation in the next 30 days, higher than 88% of all CVEs. This Node.js vulnerability: CVSS 7.7 (v3.1). Fixed upstream in Node.js 26.3.1, 24.17.0, 22.23.0. Patch in your normal monthly cycle.

Share this

Remediation#

Fixed upstream in Node.js 26.3.1, 24.17.0, 22.23.0.

Patch events

  1. This monthSecurity release

    Language runtimeNode.js

    Node.js security releases: 26.3.1, 24.17.0, 22.23.0

    Upgrade to 26.3.124.17.022.23.0

    Why: CVE-2026-48618: EPSS 3.1% with high severity (CVSS 7.7).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)3.1% (88th pct)FIRST EPSS v2026.06.15
CVSS base score7.7 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

A flaw in Node.js TLS hostname handling can cause Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismat. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

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 →