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**.
Metrics
Affected Vendors & Products
References
History
Fri, 26 Jun 2026 07:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nodejs
Nodejs nodejs |
|
| Vendors & Products |
Nodejs
Nodejs nodejs |
Fri, 26 Jun 2026 03:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Node.js Hostname Matching Inconsistency Allows Trust‑Policy Bypass in Multi‑Context mTLS |
Fri, 26 Jun 2026 01:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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**. | |
| Weaknesses | CWE-284 | |
| References |
| |
| Metrics |
cvssV3_0
|
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2026-06-26T01:14:36.981Z
Reserved: 2026-05-26T15:00:06.427Z
Link: CVE-2026-48928
No data.
No data.
No data.
OpenCVE Enrichment
Updated: 2026-06-26T07:15:16Z