What is CVE-2026-48934?
A flaw in Node.js TLS host verification can cause an attacker to bypass certification validation. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
The record classifies CVE-2026-48934 under weakness class CWE-295. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 106 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 4.3 — MEDIUM
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N - EPSS (FIRST)
- 0.2% probability of exploitation in the next 30 days, higher than 16.0% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 2.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-06-26, last modified 2026-06-29
Is CVE-2026-48934 being exploited?
It currently carries a trending score of 18 in the Threadlinqs vulnerability feed.
Affected products and versions
- nodejs: node
How to fix CVE-2026-48934
No vendor patch reference has been recorded for CVE-2026-48934 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-48934
2 tracked threats in the Threadlinqs corpus reference CVE-2026-48934, either in the campaign’s CVE list or as an indicator on the campaign record.
- Node.js Patches 11 Security Flaws Across v22.23.2, v24.18.1, v26.5.1 (HTTP/2 DoS, Permission Model Bypass, TLS/mTLS Issues) — HIGH · 2026-08-01
- Node.js June 2026 Security Release — 12 Vulnerabilities Across 22.x/24.x/26.x Including Two High-Severity TLS Authentication Bypass and WebCrypto DoS Flaws (CVE-2026-48618, CVE-2026-48933) — HIGH · 2026-06-19
Sources
Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on .