Node
Node.js is vulnerable to cross-connection memory disclosure via TLS write re-entrancy in the HTTPS request parser
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.0.0, < 22.23.5
- >= 23.0.0, < 24.22.3
- >= 25.0.0, < 26.13.1
Fixed in 22.23.5, 24.22.3, 26.13.1
Mitigation
Upgrade node to 22.23.5 or 24.22.3 or 26.13.1 or later.
References
- Vendor advisory nodejs.org/en/blog/vulnerability/november-2026…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.