All reports
High

nodejs: nodejs: Information disclosure via HTTPS parser re-entrancy

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-123864

Probability of exploitation in the next 30 days: 0.37%

FIRST EPSS · 2026-11-19

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.

A flaw was found in Node.js. An unauthenticated remote attacker can exploit a re-entrancy vulnerability in the HTTPS server to cause memory corruption and read memory belonging to other connections. Under specific request handling conditions, processing incoming encrypted data while the HTTP parser is active causes freed or out-of-bounds heap memory to be read and returned to the client. This flaw leads to information disclosure, potentially exposing sensitive data such as other users' requests and Transport Layer Security (TLS) private keys.