Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| nodejs | node | unaffected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Nodejs | Nodejs |
|
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4809-1 | nodejs security update |
Debian DSA |
DSA-6517-1 | nodejs security update |
No CVSS v4.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.216% probability within 30 days)
| 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
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nodejs
Nodejs nodejs |
|
| Vendors & Products |
Nodejs
Nodejs nodejs |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Node.js Hostname Matching Inconsistency Allows Trust‑Policy Bypass in Multi‑Context mTLS |
| 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
|