What is CVE-2026-56850?
A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
The record classifies CVE-2026-56850 under weakness class CWE-287. Its CVSS v3 base vector states that the flaw requires local access to the host, needs high-privilege credentials, needs no user interaction, and has high impact on integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 67 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 4.1 — MEDIUM
CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N - EPSS (FIRST)
- 0.0% probability of exploitation in the next 30 days, higher than 17.9% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 2.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-07-30
Is CVE-2026-56850 being exploited?
No public exploitation evidence for CVE-2026-56850 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-07-30. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.
Affected products and versions
- nodejs: node
How to fix CVE-2026-56850
No vendor patch reference has been recorded for CVE-2026-56850 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-56850
1 tracked threat in the Threadlinqs corpus references CVE-2026-56850, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.