Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to vulnerabilities
Unrated

Node.js TLS host identity verification bypass via session reuse

IdentifiersCVE-2026-48934CWE-297

CVE-2026-48934 is a medium-severity vulnerability in Node.js TLS hostname/host identity verification. According to the provided context, the flaw allows TLS host identity verification to be bypassed when a TLS session is reused with a different server name. This indicates improper binding of session reuse state to the validated peer identity, allowing previously established session parameters to be reused across connections for a different hostname/SNI context without re-validating the intended server identity.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial
ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can bypass certificate-based host identity verification and cause a client to accept an unauthorized connection as if it were the intended server. This can undermine TLS authentication guarantees and may enable unauthorized connections, spoofing, man-in-the-middle-style trust bypass, or other security boundary failures where applications rely on Node.js TLS hostname verification to authenticate remote peers.

Mitigation

If you can’t patch tonight, do this now.

Until upgrades can be applied, avoid reusing TLS sessions across connections targeting different server names or SNI values, and ensure applications do not assume session resumption preserves correct peer identity across hostname changes. Where feasible, disable or tightly constrain client-side TLS session reuse/resumption for sensitive connections and enforce additional application-layer verification of the expected peer identity. The authoritative mitigation is to upgrade to a fixed Node.js version.

Remediation

Patch, then assume compromise.

Upgrade Node.js to a fixed release. The provided context states that Node.js addressed this issue in the June 18, 2026 security release and recommends upgrading to Node.js v22.23.0, v24.17.0, or v26.3.1, as appropriate for the deployed release line. End-of-life Node.js versions should not be used in production, as they remain vulnerable.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

4 SOURCESView more in app
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Start free trial
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-48934
NVD
nvd.nist.gov/vuln/detail/CVE-2026-48934
MITRE CWE · CWE-297
cwe.mitre.org