CVE-2026-123864
Node.js: zero-length TLS write re-enters the HTTP parser and leaks heap memory into the request body
Technology
Node.js
CVSS Score
8.1 / 10.0
Affected Versions
>=22.0.0 <22.23.5; >=24.0.0 <24.22.3; >=26.0.0 <26.13.1
Upstream Fix
22.23.5; 24.22.3; 26.13.1
Published
November 11, 2026
OSSeva Coverage
Fixed upstream
Description
TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes. Issued from JavaScript inside the HTTP parser's on_body callback, that decrypts the next TLS record while the parser is mid-body, re-entering llhttp_execute() and causing a use-after-free and an out-of-bounds heap read. The server copies the freed or unrelated memory into the request body, which can expose TLS private keys and other users' requests. It needs a handler that calls res.flushHeaders() before the request body ends and later res.end() with a non-empty chunk; cleartext node:http is not affected. Rated High by Node.js; CVSS is the CNA's score as recorded at NVD. Fixed in 22.23.5, 24.22.3 and 26.13.1.
Is your Node.js deployment affected?
If you're running >=22.0.0 <22.23.5; >=24.0.0 <24.22.3; >=26.0.0 <26.13.1, you need this patch. Book a discovery call to get covered.
Get a quote
Running Node.js >=22.0.0 <22.23.5; >=24.0.0 <24.22.3; >=26.0.0 <26.13.1?
Send your work email and a senior engineer will tell you whether this CVE applies to your versions and who patches it. Reply within 1 business day.
Prefer to talk or read more first?