Node.js HTTPS memory disclosure Flaw CVE-2026-123864: Update Now
Published November 11, 2026 · Last updated November 11, 2026
The short version: CVE-2026-123864 is a high-severity security flaw in Node.js HTTPS memory disclosure. The National Vulnerability Database (NVD) published it on November 11, 2026, and the score it lists is 8.1 out of 10. When FraudMeNot checked on November 11, 2026, CISA had not added CVE-2026-123864 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.
CVE-2026-123864 is a high-severity memory disclosure flaw in Node.js HTTPS servers. According to the Node.js project, an unauthenticated client can use it to "read memory belonging to other connections, including TLS private keys and other users' requests." The fix shipped on November 11, 2026, in Node.js 22.23.5, 24.22.3 and 26.13.1, as part of that day's security release.
What goes wrong
The bug sits where Node.js decrypts incoming TLS data and passes it to its HTTP parser, llhttp. The project's advisory explains that when an application asks the TLS layer to write zero bytes, the internal function TLSWrap::DoWrite() immediately calls ClearOut(). If that zero-length write happens from JavaScript that is already running inside the parser's on_body callback, ClearOut() decrypts the next TLS record while the parser is still in the middle of a request body.
That re-enters the parser, which the advisory says causes "a use-after-free and an out-of-bounds heap read." The weakness is listed as CWE-416, Use After Free. The practical result, in the words of the advisory's title, is that "the server copies its own heap into the request body." Heap memory in a busy server can hold data from other people's connections, which is why the advisory warns about private keys and other users' requests.
When a server is exposed
Not every HTTPS server built on Node.js can be attacked. The advisory lists two conditions:
- A route that triggers the bug. Somewhere in the application, a handler has to call
res.flushHeaders()before the request body ends, and then later callres.end()with a non-empty chunk. - A route that reveals the leak. The attacker reads the leaked memory through "any ordinary route that echoes or stores a request body," for example an endpoint that returns submitted data or saves it where the attacker can view it later.
Plain HTTP servers using node:http are not affected; the problem only occurs with HTTPS. No login is needed, because the attacker only has to send requests.
Affected and fixed versions
According to the CVE record, these versions are affected:
- Node.js before 22.23.5 on the 22.x line.
- Node.js 23.0.0 up to, but not including, 24.22.3.
- Node.js 25.0.0 up to, but not including, 26.13.1.
The Node.js project says the issue "affects all users in active release lines: 22.x, 24.x, 26.x." The project also notes that "End-of-Life versions are always affected when a security release occurs," so anything older than the supported lines should be treated as vulnerable with no fix coming.
Severity and who scored it
The OpenJS Foundation, the CVE Numbering Authority for Node.js, scored the flaw CVSS 3.0 8.1 (High). The vector is AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H: a network attack with high complexity, no privileges and no user interaction. NVD shows that score as Secondary and had not added its own assessment when checked on November 11. The flaw is not in CISA's Known Exploited Vulnerabilities catalog, and the Node.js project does not say it has been exploited.
The project credits Chris Rohlf, working with Claude and Anthropic Research, for the report, and the maintainer mcollina for the fix.
Timeline
- November 4, 2026: the Node.js project posted an advance notice on its blog that new versions of the 26.x, 24.x and 22.x lines would be released "on, or shortly after, Wednesday, November 11, 2026," and that the highest severity issue fixed was HIGH. That notice did not name or describe any of the issues.
- November 6, 2026: the CVE identifier was reserved.
- November 11, 2026: Node.js updated the post with the full advisory and published the fixed releases. The CVE record went public at 1:17 PM EST.
The rest of the November 11 release
The same release fixed sixteen Node.js vulnerabilities in total. Seven are rated high, and several of the others also involve HTTP/2 and TLS. They include a remote crash in HTTP/2 session teardown (CVE-2026-123863), a TLS 1.2 renegotiation trick that bypasses per-hostname client certificate checks (CVE-2026-123872), and a use-after-free when files are served with respondWithFile() (CVE-2026-123874). The release also updates the bundled llhttp, undici and sqlite dependencies to address public vulnerabilities. Upgrading to the fixed versions covers all of them at once.
What to do
- Teams running Node.js HTTPS servers: upgrade now. Move to Node.js 22.23.5, 24.22.3 or 26.13.1 or later on your release line, then restart every process, because a running server keeps the old code until it restarts.
- Check your container images and build pipelines. Rebuild images that pin a Node.js version or base image, and confirm with
node --versionin production that the new build is what is actually running. - Upgrade end-of-life installs. Servers on unsupported release lines will not get a fix. Plan a move to a supported line.
- Developers: review risky handler patterns while you upgrade. Look for handlers that call
res.flushHeaders()before the request body ends and later finish withres.end()and a chunk. Note which routes echo or store request bodies. This helps you judge exposure, but it is not a substitute for the update. - Security teams: consider rotating TLS keys on exposed servers. Because the bug can leak private keys and the advisory gives no way to tell whether it was used, rotating certificates and keys on internet-facing Node.js HTTPS servers that ran affected versions is a reasonable precaution.
Sources: Node.js project, "Wednesday, November 11, 2026 Security Releases"; CVE record CVE-2026-123864 published by the OpenJS Foundation; NVD record for CVE-2026-123864.
What the official record says about CVE-2026-123864
The record was filed by ce714d77-add3-4f53-aff5-83d477b104bb. In its own words: "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."
Why HTTPS memory disclosure admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). ce714d77-add3-4f53-aff5-83d477b104bb rated CVE-2026-123864 8.1 (High) under CVSS 3.0. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is low, to keeping data unaltered is low, and to keeping HTTPS memory disclosure running is high. Scoring string: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H.
Affected HTTPS memory disclosure releases
According to the record, these releases are vulnerable:
- 0.0.0 up to, but not including, 22.23.5
- 23.0.0 up to, but not including, 24.22.3
- 25.0.0 up to, but not including, 26.13.1
The type of bug behind CVE-2026-123864
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-416, Use After Free. MITRE describes this class of bug as follows: "The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer."
Vendor remediation for CVE-2026-123864
The vendor advisory remediation for operators of HTTPS memory disclosure, quoted for this page, is: "Upgrade Node.js to 22.23.5, 24.22.3 or 26.13.1 or later, then restart all Node.js processes."
What to do about it
- Update now: Upgrade Node.js to 22.23.5, 24.22.3 or 26.13.1 or later, then restart all Node.js processes.
- Who should act: IT teams, managed service providers, and developers who run or ship HTTPS memory disclosure. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from Node.js (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from November 11, 2026 onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-123864. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-123864 record details from CISA and NVD
- Attack complexity for CVE-2026-123864: high
- CVE-2026-123864 CVSS scope: changed
- NVD sub-scores for CVE-2026-123864: exploitability 2.2, impact 5.3.
- Who mapped the weakness type: ce714d77-add3-4f53-aff5-83d477b104bb (Secondary)
- References in the NVD record: 2.
Dates to know
- November 11, 2026: NVD publishes CVE-2026-123864.
- November 11, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-123864 is not listed.
- November 11, 2026: most recent NVD update (record status: Received).
Official references
Links listed in the NVD record (labels in brackets come from NVD):
- cna.openjsf.org/security-advisories.html
- nodejs.org/en/blog/vulnerability/november-2026-security-releases
Sources
General education only, not security advice. Facts checked against the sources above on the date shown.