This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sat, 27 Jun 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Node.js Hostname Matching Inconsistency Allows Trust‑Policy Bypass in Multi‑Context mTLS | Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency |
| Weaknesses | CWE-289 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Fri, 26 Jun 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
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-26T13:36:28.487Z
Reserved: 2026-05-26T15:00:06.427Z
Link: CVE-2026-48928
Updated: 2026-06-26T13:36:24.879Z
No data.
OpenCVE Enrichment
Updated: 2026-06-27T01:30:09Z