CVE-2026-56850·Node.js vulnerability
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**.
- Severity
- medium
- Software
- Node.js
- Fixed in
- 18.20.4+dfsg-1~deb12u3
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at <0.1% — in the bottom 1% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 26.0.0
Until: 26.5.0
Fixed in: 18.20.4+dfsg-1~deb12u3
How to fix this CVE
Update Node.js to version 18.20.4+dfsg-1~deb12u3 or later to resolve the HTTPS Agent certificate collision vulnerability. This patch prevents unintended reuse of mTLS client certificates across different connection contexts, ensuring each request uses the correct certificate identity. Verify the update is applied before resuming production services that rely on mutual TLS authentication.
sudo dnf update nodejsDefensia detects this vulnerability
How to check if you are affected
- Run `node --version` to check the currently installed Node.js version; vulnerable versions are 26.0.0–26.5.0, 24.x, and 22.x below the fix
- Review your application's HTTPS Agent configuration by searching source code for `https.Agent` and `pfx` or `cert`/`key` parameters to identify if mTLS is enabled
- Search application and proxy logs for multiple requests from the same connection with different TLS certificate subjects using `grep -i 'subject=' /var/log/app.log | sort | uniq -c` to detect certificate reuse patterns
- Confirm the patch by running `node --version` again after updating; the version should be 18.20.4 or higher, and verify `npm list` shows the correct nodejs package version installed
FAQ
What is CVE-2026-56850?
This vulnerability allows Node.js HTTPS Agent to incorrectly reuse the same mTLS client certificate across multiple requests that should have used different certificates. The flaw stems from how the agent caches connections using PFX objects, causing certificate identity confusion when multiple client identities are configured.
Is CVE-2026-56850 being actively exploited?
No, CVE-2026-56850 is not currently listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available. However, the vulnerability poses a serious risk to applications handling sensitive mTLS-authenticated connections and should still be prioritized for patching.
What versions of Node.js are affected by CVE-2026-56850?
Node.js versions 26.0.0 through 26.5.0, and earlier versions in the 24.x and 22.x release lines are affected. The fix is available in version 18.20.4+dfsg-1~deb12u3 and later releases.
How do I check if my server is vulnerable to CVE-2026-56850?
Run `node --version` and compare the output against the affected ranges (22.x–24.x and 26.0.0–26.5.0). If your version falls within these ranges, your server is vulnerable. Also verify that your Node.js application uses HTTPS Agent with mTLS by checking your codebase for `https.Agent` and `pfx` configuration.
Does Defensia detect CVE-2026-56850?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Node.js is installed on a monitored server, CVE-2026-56850 will appear in your dashboard with remediation steps.
Related Node.js CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-56850. Free for 1 server.
Get started free