VulnSocial

CVE-2026-48928Disclosure(nodejs / node.js)

LOWCVSS 5.4 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD 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**.

nodejs CVEsBack to dashboard
0.0/ 10 priority

Sources & remediation

Patch / fix
Weakness type (CWE)
CWE-284

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • node.js

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Vendors
nodejs
Products
node.js

3 versions affected across 1 product

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-06-26: 1Technical Details · 2026-06-26: 106-26
Signal classification1 categories
Disclosure
1100.0%
Referenced assets1 URL
By indicator
Full discourse1 post
  • Vulmon Vulnerability Feed@VulmonFeeds
    Disclosure

    CVE-2026-48928 Hostname Matching Inconsistency in Node.js Causes mTLS Trust-Policy Bypass https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-48928

    Post summary

    The post announces CVE-2026-48928, a hostname matching flaw in Node.js that allows an attacker to bypass mTLS trust policies, without mentioning any PoC, exploit code, active exploitation, or patch.

    00000105
    4.1K followersView on X
CPE platform detail3 entries

3 of 3 entries

PartVendorProductVersionTarget SWTarget HW
Appnodejsnode.js22.22.3--
Appnodejsnode.js24.16.0--
Appnodejsnode.js26.3.0--

Explore more

Back to dashboardnodejs CVEsnode.js vulnerabilities