CVE-2026-48934

nodejs: Node.js: Certification validation bypass in TLS host verification

Published Jun 26, 2026 CVSS 3.0 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
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**.

Analysis

AI-generated

Technical impact

A flaw in Node.js TLS host verification allows an attacker to bypass certificate validation, potentially enabling man‑in‑the‑middle attacks or impersonation of trusted servers. The vulnerability can compromise the confidentiality and integrity of data transmitted over TLS connections. It results in a moderate CVSS score of 4.3, indicating a non‑critical but still meaningful risk to applications relying on Node.js for secure communication.

Affected Systems

All supported release lines of Node.js are impacted, specifically Node.js 22, Node.js 24, and Node.js 26. The flaw exists in the core TLS implementation and applies to any application using the default certificate validation behavior.

Risk and Exploitability

The CVSS score reflects moderate severity. The EPSS score is below 1 %, indicating a very low but non‑zero probability of exploitation. The vulnerability is not listed in the CISA KEV catalog, suggesting no publicly confirmed exploits yet. The vector requires an attacker to establish a TLS session with the vulnerable Node.js instance, possibly over a network connection, to exploit the host verification bypass. While the exact exploitation process is not described, the risk remains that an attacker could hijack traffic if the application trusts unverified certificates.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Node.js to the latest patched release for the relevant 22 or newer series.
  • If an immediate upgrade is not possible, temporarily disable host verification by setting `rejectUnauthorized` to false in TLS options or using the `NODE_TLS_REJECT_UNAUTHORIZED=0` the added risk.
  • Implement explicit certificate pinning or additional validation logic in the application so that the host name is checked against the server’s certificate after the TLS handshake.

Generated by OpenCVE AI on August 12, 2026 at 05:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4809-1 nodejs security update
Debian DSA Debian DSA DSA-6517-1 nodejs security update
History
Type Values Removed Values Added
Weaknesses CWE-297
Type Values Removed Values Added
Title Node.js TLS Host Verification Bypass in Node.js 22, 24, and 26 nodejs: Node.js: Certification validation bypass in TLS host verification
Weaknesses CWE-295
References
Metrics threat_severity

None

threat_severity

Moderate

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Nodejs
Nodejs nodejs
Vendors & Products Nodejs
Nodejs nodejs
Type Values Removed Values Added
Title Node.js TLS Host Verification Bypass in Node.js 22, 24, and 26
Weaknesses CWE-297
Type Values Removed Values Added
Description 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**.
References
Metrics cvssV3_0

{'score': 4.3, 'vector': 'CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
hackerone
Published
Updated
Jun 29, 2026, 12:40 PM
Reserved
May 26, 2026, 3:00 PM
Status
Modified
Published
Jun 26, 2026, 2:16 AM
Modified
Oct 25, 2026, 10:10 PM
Severity
Moderate
Public date
Jun 26, 2026, 1:14 AM