{"id":"CVE-2026-123864","state":"PUBLISHED","title":"Node.js is vulnerable to cross-connection memory disclosure via TLS write re-entrancy in the HTTPS request parser","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.","publishedAt":"2026-11-11T18:17:56.773Z","updatedAt":"2026-11-16T21:47:41.707Z","severity":{"score":8.1,"label":"High","version":"3.0","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H","source":"openjs"},"assigner":"openjs","products":["nodejs node"],"affected":[{"vendor":"nodejs","product":"node","defaultStatus":"unaffected","versions":[{"version":"0.0.0","status":"affected","lessThan":"22.23.5","versionType":"semver"},{"version":"23.0.0","status":"affected","lessThan":"24.22.3","versionType":"semver"},{"version":"25.0.0","status":"affected","lessThan":"26.13.1","versionType":"semver"}]}],"references":["https://nodejs.org/en/blog/vulnerability/november-2026-security-releases","https://cna.openjsf.org/security-advisories.html"],"weaknesses":["CWE-416"],"ingestedAt":"2026-11-16T21:56:07.288Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/123xxx/CVE-2026-123864.json","commit":"71b39a7b46c402025297bfde9fc2069f184d0fa3","baselineCommit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-123864","state":"PUBLISHED","datePublished":"2026-11-11T18:17:56.773Z","dateUpdated":"2026-11-16T21:47:41.707Z","assignerShortName":"openjs","assignerOrgId":"ce714d77-add3-4f53-aff5-83d477b104bb","dateReserved":"2026-11-06T16:13:33.715Z"},"containers":{"cna":{"title":"Node.js is vulnerable to cross-connection memory disclosure via TLS write re-entrancy in the HTTPS request parser","descriptions":[{"lang":"en","value":"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":[{"vendor":"nodejs","product":"node","defaultStatus":"unaffected","versions":[{"version":"0.0.0","status":"affected","lessThan":"22.23.5","versionType":"semver"},{"version":"23.0.0","status":"affected","lessThan":"24.22.3","versionType":"semver"},{"version":"25.0.0","status":"affected","lessThan":"26.13.1","versionType":"semver"}]}],"references":[{"url":"https://nodejs.org/en/blog/vulnerability/november-2026-security-releases","tags":["vendor-advisory"]},{"url":"https://cna.openjsf.org/security-advisories.html"}],"metrics":[{"format":"CVSS","cvssV3_0":{"version":"3.0","vectorString":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H","baseScore":8.1,"baseSeverity":"HIGH"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-416","lang":"en","type":"CWE","description":"Use After Free"}]}],"providerMetadata":{"shortName":"openjs","orgId":"ce714d77-add3-4f53-aff5-83d477b104bb","dateUpdated":"2026-11-11T18:17:56.773Z"},"credits":[{"lang":"en","value":"Chris Rohlf in collaboration with Claude and Anthropic Research","type":"reporter"},{"lang":"en","value":"mcollina","type":"remediation developer"},{"lang":"en","value":"ShogunPanda","type":"remediation reviewer"},{"lang":"en","value":"pimterry","type":"remediation reviewer"},{"lang":"en","value":"aduh95","type":"coordinator"}],"x_generator":{"engine":"nodejs-private/security-release publish-cves"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-11-16T21:47:29.716063Z","id":"CVE-2026-123864","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-11-16T21:47:41.707Z"}}]}}}