CVE-2026-56850
What it is
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**.
At a glance
- Exploitability
- Can be exploited locally on the machine with an admin-level account. High risk of data tampering.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 4.4 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-287 · Improper authentication
- Record status
- Analyzed
Affected
- Nodejs node.js ≤ 22.23.1
- Nodejs node.js ≤ 24.18.0
- Nodejs node.js ≤ 26.5.0
Attack profile CVSS 3.1 · 4.4
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-56850.md and follow it. Check whether this project is affected by CVE-2026-56850. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
