CVE-2026-123864: Unauthenticated cross-connection memory disclosure in Node.js HTTPS
CVE-2026-123864 is a re-entrancy vulnerability in the HTTPS implementation of Node.js 22.x before 22.23.5, 24.x before 24.22.3, and 26.x before 26.13.1. TLSWrap::DoWrite() directly invokes ClearOut() for zero-byte writes. When JavaScript issues such a write inside the HTTP parser's on_body callback, ClearOut() can decrypt another TLS record while request-body parsing remains active, re-entering llhttp_execute(). This causes a use-after-free and an out-of-bounds heap read, allowing freed or unrelated heap memory to be processed as request-body data and disclosed through application responses or storage. Cleartext node:http is unaffected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
An unauthenticated network client can obtain heap memory belonging to other connections in the same Node.js process. Potentially exposed information includes TLS private keys and other users' request data, compromising confidentiality across connections. Leaked bytes may also contaminate stored request bodies or associated logs. Exposure depends on application-handler behavior and the availability of an attacker-readable request-body echo or storage route; disclosure of any particular secret is not guaranteed.
Mitigation
If you can’t patch tonight, do this now.
No supported workaround is identified. Pending patching, restrict access to affected HTTPS listeners and isolate services to reduce exposure; these are interim risk reductions, not validated substitutes for the fix. Review handlers for early res.flushHeaders() calls followed by res.end() with non-empty data, and identify attacker-readable routes that echo or store request bodies. Cleartext node:http does not execute the vulnerable path, but disabling transport encryption is not an appropriate mitigation.
Remediation
Patch, then assume compromise.
Upgrade to Node.js 22.23.5, 24.22.3, or 26.13.1, or a later patched release in the corresponding supported branch. Alternatively, install the applicable distribution security update containing the fix. Rebuild and redeploy affected container images, restart Node.js processes, and verify the running runtime version. The fix prevents empty writes from causing nested TLS/parser execution and protects parser-buffer state. Migrate unsupported release lines to a supported patched version. Separately assess whether potentially exposed TLS keys, credentials, or session material require rotation or revocation; updating does not invalidate previously disclosed secrets.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-123864 exploited in the wild?
- As of Nov 16, 2026, Mallory has no reports of CVE-2026-123864 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-123864?
- As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-123864.
- Is there a patch for CVE-2026-123864?
- Upgrade to Node.js 22.23.5, 24.22.3, or 26.13.1, or a later patched release in the corresponding supported branch. Alternatively, install the applicable distribution security update containing the fix.
- How severe is CVE-2026-123864?
- CVE-2026-123864 has a CVSS v3 score of 8.1 (High) and an EPSS score of 0.36% (31st percentile) as of Nov 16, 2026.
Recent activity
30 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.