CVE-2026-48928
Analyzed Analyzed - Analysis Complete
Hostname Matching Bypass in Node.js mTLS

Publication date: 2026-06-26

Last updated on: 2026-06-26

Assigner: HackerOne

Description
A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-26
Last Modified
2026-06-26
Generated
2026-06-27
AI Q&A
2026-06-26
EPSS Evaluated
2026-06-26
NVD
CVE-2026-48928
EUVD
EUVD-2026-39613
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
nodejs node.js 26.3.0
nodejs node.js 24.16.0
nodejs node.js 22.22.3
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is caused by an inconsistency in how Node.js matches hostnames in multi-context mutual TLS (mTLS) setups. This inconsistency can lead to a bypass of the trust policy, meaning that the system may incorrectly trust a connection that should not be trusted.

Impact Analysis

The vulnerability can impact you by allowing an attacker to bypass trust policies in multi-context mTLS environments. This could lead to unauthorized access or communication with services that rely on hostname verification for security, potentially compromising the confidentiality and integrity of data.

Mitigation Strategies

To mitigate this vulnerability, users are advised to update Node.js to the latest patched versions in the supported release lines: 22.x, 24.x, and 26.x.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48928. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart