CVE-2026-123864
Last modified
CVE-2026-123864 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScript running inside the HTTP parser's on_body callback, ClearOut() decrypts the next TLS record while the parser is still mid-body, re-entering llhttp_execute() and causing a use-after-free and an out-of-bounds heap read. EPSS estimates a 0.33% chance of exploitation in the next 30 days.
Description
A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScript running inside the HTTP parser's on_body callback, ClearOut() decrypts the next TLS record while the parser is still mid-body, re-entering llhttp_execute() and causing a use-after-free and an out-of-bounds heap read. The server then copies that freed or unrelated heap memory into the response for the request body. Triggering it requires a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, and reading the leaked memory requires any ordinary route that echoes or stores a request body. Cleartext node:http is not affected. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| nodejs | node | >= 0.0.0, < 22.23.5; >= 23.0.0, < 24.22.3; >= 25.0.0, < 26.13.1 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-123864?
How severe is CVE-2026-123864?
How do I fix CVE-2026-123864?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-123859When identifier escaping is disabled through a non-default c…8.1
- CVE-2026-12386Improper null termination vulnerability in TUBITAK BILGEM So…3.9
- CVE-2026-123860Improper Neutralization of Script-Related HTML Tags in a Web…5.3
- CVE-2026-123861Authorization Bypass Through User-Controlled Key vulnerabili…5.3
- CVE-2026-123862An uncatchable exception in the Node.js zlib streaming API l…2.9
- CVE-2026-123863A reachable assertion in Node.js HTTP/2 session teardown let…8.2
- CVE-2026-123865An unauthenticated HTTP/2 client can permanently leak Node.j…7.5
- CVE-2026-123866A use-after-free in Node.js HTTP/2 stream teardown can leak …7.5
- CVE-2026-123867A per-host mutual-TLS authorization bypass in Node.js lets a…4.2
- CVE-2026-123868An unauthenticated HTTP/2 client can exhaust Node.js server …5.9
- CVE-2026-12387Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel D…5.1
- CVE-2026-123870The otterdog webapp evaluates a format-string built from the…9.5
Are you affected by CVE-2026-123864?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
