Skip to main content
EPSS 0.2%top 89%

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

0
Medium
Published: 06/26/2026 (06/26/2026, 02:16:00 UTC)
Source: GCVE Database
Product: nodejs

Description

An inconsistency in hostname matching in Node.js can cause a trust-policy bypass in multi-context mutual TLS (mTLS) setups. This vulnerability affects specific versions in the Node.js 22, 24, and 26 release lines, as well as certain Ubuntu package versions. A patch is available to address this issue.

CVSS v3.1

Score 5.4medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected software

Bitnamimore threats →ghsa
node
pkg:bitnami/node
Affected versions
>=22.22.3 <22.23.0>=24.16.0 <24.17.0>=26.3.0 <26.3.1
Ubuntu:Pro:14.04:LTSmore threats →ghsa
nodejs
pkg:deb/ubuntu/nodejs?arch=source&distro=esm-infra-legacy/trusty
Affected versions
=0.10.15~dfsg1-4=0.10.21~dfsg1-1=0.10.22~dfsg1-2=0.10.23~dfsg1-1=0.10.23~dfsg1-2=0.10.23~dfsg1-3=0.10.24~dfsg1-1=0.10.25~dfsg2-2=0.10.25~dfsg2-2ubuntu1=0.10.25~dfsg2-2ubuntu1.2=0.10.25~dfsg2-2ubuntu1.2+esm1=0.10.25~dfsg2-2ubuntu1.2+esm2
Ubuntu:Pro:16.04:LTSmore threats →ghsa
nodejs
pkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/xenial
Affected versions
=0.10.25~dfsg2-2ubuntu1=4.2.2~dfsg-1=4.2.3~dfsg-1=4.2.4~dfsg-1ubuntu1=4.2.4~dfsg-2=4.2.6~dfsg-1ubuntu1=4.2.6~dfsg-1ubuntu4=4.2.6~dfsg-1ubuntu4.1=4.2.6~dfsg-1ubuntu4.2=4.2.6~dfsg-1ubuntu4.2+esm1=4.2.6~dfsg-1ubuntu4.2+esm2=4.2.6~dfsg-1ubuntu4.2+esm3
Ubuntu:Pro:18.04:LTSmore threats →ghsa
nodejs
pkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/bionic
Affected versions
=6.11.4~dfsg-1ubuntu1=6.11.4~dfsg-1ubuntu2=6.12.0~dfsg-1ubuntu1=6.12.0~dfsg-2ubuntu1=6.12.0~dfsg-2ubuntu2=8.10.0~dfsg-2=8.10.0~dfsg-2ubuntu0.2=8.10.0~dfsg-2ubuntu0.3=8.10.0~dfsg-2ubuntu0.4=8.10.0~dfsg-2ubuntu0.4+esm1=8.10.0~dfsg-2ubuntu0.4+esm2=8.10.0~dfsg-2ubuntu0.4+esm3=8.10.0~dfsg-2ubuntu0.4+esm4=8.10.0~dfsg-2ubuntu0.4+esm5=8.10.0~dfsg-2ubuntu0.4+esm6
Ubuntu:Pro:20.04:LTSmore threats →ghsa
nodejs
pkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/focal
Affected versions
=10.15.2~dfsg-2ubuntu1=10.17.0~dfsg-2ubuntu4=10.17.0~dfsg-2ubuntu6=10.19.0~dfsg-3ubuntu1=10.19.0~dfsg-3ubuntu1.1=10.19.0~dfsg-3ubuntu1.2=10.19.0~dfsg-3ubuntu1.3=10.19.0~dfsg-3ubuntu1.5=10.19.0~dfsg-3ubuntu1.6=10.19.0~dfsg-3ubuntu1.6+esm2
Ubuntu:Pro:22.04:LTSmore threats →ghsa
nodejs
pkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/jammy
Affected versions
=12.22.5~dfsg-5ubuntu1=12.22.7~dfsg-2ubuntu1=12.22.7~dfsg-2ubuntu3=12.22.9~dfsg-1ubuntu2=12.22.9~dfsg-1ubuntu3=12.22.9~dfsg-1ubuntu3.1=12.22.9~dfsg-1ubuntu3.2=12.22.9~dfsg-1ubuntu3.3=12.22.9~dfsg-1ubuntu3.4=12.22.9~dfsg-1ubuntu3.5=12.22.9~dfsg-1ubuntu3.6=12.22.9~dfsg-1ubuntu3.6+esm2
Ubuntu:24.04:LTSmore threats →ghsa
nodejs
pkg:deb/ubuntu/nodejs?arch=source&distro=noble
Affected versions
=18.13.0+dfsg1-1ubuntu2=18.19.1+dfsg-2ubuntu4=18.19.1+dfsg-6ubuntu1=18.19.1+dfsg-6ubuntu2=18.19.1+dfsg-6ubuntu5
Ubuntu:25.10more threats →ghsa
nodejs
pkg:deb/ubuntu/nodejs?arch=source&distro=questing
Affected versions
=20.18.1+dfsg-1ubuntu2=20.19.2+dfsg-1=20.19.4+dfsg-1
Ubuntu:26.10more threats →ghsa
nodejs
pkg:deb/ubuntu/nodejs?arch=source&distro=stonking
Affected versions
=22.22.1+dfsg+~cs22.19.15-1ubuntu1=24.16.0+dfsg+~cs24.13.1-2ubuntu1=24.18.0+dfsg+~cs24.13.2-1ubuntu1=24.19.0+dfsg+~cs24.13.3-1ubuntu1
Ubuntu:26.04:LTSmore threats →ghsa
nodejs
pkg:deb/ubuntu/nodejs?arch=source&distro=resolute
Affected versions
=20.19.4+dfsg-1=20.19.5+dfsg+~cs20.19.12-4=22.21.1+dfsg+~cs22.19.0-6ubuntu4=22.22.0+dfsg+~cs22.19.6-1ubuntu2=22.22.0+dfsg+~cs22.19.13-2ubuntu1=22.22.1+dfsg+~cs22.19.15-1ubuntu1

Run 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

AILast updated: 10/18/2026, 05:33:24 UTC

Technical Analysis

CVE-2026-48928 describes a vulnerability in Node.js where an inconsistency in hostname matching logic leads to a trust-policy bypass in multi-context mTLS configurations. This flaw allows an attacker to circumvent trust policies by exploiting the hostname verification process. The issue affects specific versions of Node.js 22, 24, and 26 release lines, along with certain Ubuntu package versions. The vulnerability has a CVSS 3.1 base score of 5.4, indicating medium severity. A patch is available for the affected versions to correct the hostname matching behavior and prevent trust-policy bypass.

Potential Impact

The vulnerability allows bypassing trust policies in multi-context mTLS setups due to improper hostname matching. This could lead to unauthorized entities being trusted in TLS connections, potentially compromising the integrity of secure communications. However, the impact is limited to scenarios using multi-context mTLS configurations and requires local privileges (PR:L) with no user interaction (UI:N). The confidentiality and integrity impacts are low, with no availability impact.

Mitigation Recommendations

A patch is available for the affected Node.js versions and Ubuntu package versions. Users should apply the official updates to their Node.js installations to remediate this vulnerability. No additional mitigation steps are indicated beyond applying the patch.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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
State
PUBLISHED

Threat ID: 6aa005faacd9273b49ab687b

Added to database: 09/08/2026, 12:56:26 UTC

Last enriched: 10/18/2026, 05:33:24 UTC

Last updated: 10/21/2026, 13:20:22 UTC

Views: 68

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses