Medium 4.2Published Jun 25, 2026

CVE-2026-48928A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups.

Updated under an hour ago (Oct 27, 2026, 10:23 AM ET)

Does this affect you?

It affects nodejs node and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for nodejs node

Exploited in the last 30 days

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: 4.2 MEDIUM (v3.0, CNA)CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Weakness (CWE): CWE-284
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: hackerone
NVD analysis: Analyzed
Record last updated: Jun 26, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

nodejs node nodejs:node (from the name)	from 22.22.3 through 22.22.3; from 24.16.0 through 24.16.0; from 26.3.0 through 26.3.0	CNA record
nodejs node.js nodejs:node.js	22.22.3; 24.16.0; 26.3.0	NVD

References

References

https://nodejs.org/en/blog/vulnerability/june-2026-security-releases	patch, vendor-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.