CVE-2026-48928: nodejs vulnerability
nodejs · node
Affected: nodejs · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 12% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- nodejs · nodefrom 22.22.3 up to and including 22.22.3; from 24.16.0 up to and including 24.16.0; from 26.3.0 up to and including 26.3.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- nodejs
- Published
- June 2026
- Bounty reports
- 1 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2026-48928
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- Uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matchingNode.js · 2026 · medium severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2026-48928 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.