A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. (CVE-2026-48928)
An inconsistency in Node.js hostname matching can lead to a trust-policy bypass in multi-context mutual TLS (mTLS) setups. This vulnerability affects specific versions of Node.js 22, 24, and 26 release lines. It allows bypassing trust policies due to hostname matching issues in mTLS configurations. A patch is available for the affected versions.
AI Analysis
Technical Summary
CVE-2026-48928 describes a vulnerability in Node.js where an inconsistency in hostname matching logic causes a trust-policy bypass in multi-context mTLS setups. This flaw affects Node.js versions >=22.22.3 <22.23.0, >=24.16.0 <24.17.0, and >=26.3.0 <26.3.1. The vulnerability could allow an attacker to bypass trust policies that rely on hostname verification in mTLS, potentially undermining the security guarantees of TLS connections in multi-context environments. No CVSS score is provided, but the severity is assessed as medium. A patch is available to address this issue.
Potential Impact
The vulnerability allows bypassing trust policies in multi-context mTLS setups due to hostname matching inconsistencies. This could weaken the authentication guarantees of TLS connections, potentially allowing unauthorized entities to be trusted in contexts where hostname verification is critical. There are no known exploits in the wild at this time.
Mitigation Recommendations
A patch is available for the affected Node.js versions. Users should upgrade to versions >=22.23.0, >=24.17.0, or >=26.3.1 to remediate the vulnerability. Applying the official fix will resolve the hostname matching inconsistency and prevent trust-policy bypass in multi-context mTLS setups.
A inconsistency in Node.js hostname matching can cause a trust-policy bypass in multi-context mTLS setups. (CVE-2026-48928)
Description
An inconsistency in Node.js hostname matching can lead to a trust-policy bypass in multi-context mutual TLS (mTLS) setups. This vulnerability affects specific versions of Node.js 22, 24, and 26 release lines. It allows bypassing trust policies due to hostname matching issues in mTLS configurations. A patch is available for the affected versions.
Affected software
pkg:bitnami/nodeRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-48928 describes a vulnerability in Node.js where an inconsistency in hostname matching logic causes a trust-policy bypass in multi-context mTLS setups. This flaw affects Node.js versions >=22.22.3 <22.23.0, >=24.16.0 <24.17.0, and >=26.3.0 <26.3.1. The vulnerability could allow an attacker to bypass trust policies that rely on hostname verification in mTLS, potentially undermining the security guarantees of TLS connections in multi-context environments. No CVSS score is provided, but the severity is assessed as medium. A patch is available to address this issue.
Potential Impact
The vulnerability allows bypassing trust policies in multi-context mTLS setups due to hostname matching inconsistencies. This could weaken the authentication guarantees of TLS connections, potentially allowing unauthorized entities to be trusted in contexts where hostname verification is critical. There are no known exploits in the wild at this time.
Mitigation Recommendations
A patch is available for the affected Node.js versions. Users should upgrade to versions >=22.23.0, >=24.17.0, or >=26.3.1 to remediate the vulnerability. Applying the official fix will resolve the hostname matching inconsistency and prevent trust-policy bypass in multi-context mTLS setups.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-node-2026-48928
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2026-48928"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- Medium
- Cvss Version
- null
Threat ID: 6aa005faacd9273b49ab687b
Added to database: 09/08/2026, 12:56:26 UTC
Last enriched: 09/08/2026, 13:35:30 UTC
Last updated: 09/09/2026, 01:14:05 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.