{"id":"EM-20261111-S8M5","url":"https://cyber.eventmonitor.net/incident/EM-20261111-S8M5/node-js-https-vulnerability-cve-2026-123864/","type":"cve","title":"Node.js HTTPS Vulnerability (CVE-2026-123864)","subtitle":"CVE-2026-123864","subject":"CVE-2026-123864","status":"Developing","severity":"high","affected":[],"headline":null,"born":"2026-11-11T19:17:32.790Z","firstSignal":"2026-11-11T18:17:56.000Z","lastSignal":"2026-11-11T19:17:32.790Z","updated":"2026-11-12T00:31:06.720Z","revision":1,"life":[{"status":"Born","at":"2026-11-11T19:17:32.790Z","why":"second independent source: C6 NVD CVE API 2.0"},{"status":"Developing","at":"2026-11-11T19:17:32.790Z","why":"signals keep joining"}],"changeLog":[{"at":"2026-11-11T18:17:56.000Z","what":"First signal: C41 Red Hat Security Data"},{"at":"2026-11-11T19:17:32.790Z","what":"Born: second source, C6 NVD CVE API 2.0. Page EM-20261111-S8M5 created."}],"stages":[{"name":"Disclosed","at":"2026-11-11T19:17:32.790Z","detail":"C6 NVD published"},{"name":"Scored","at":"2026-11-11T19:17:32.790Z","detail":"CVSS 8.1"},{"name":"Exploited","at":null,"detail":"No exploitation reported"},{"name":"Advisories","at":null,"detail":"None yet"},{"name":"Vendor Response","at":"2026-11-11T18:17:56.000Z","detail":"C41 published"},{"name":"Resolved","at":null,"detail":"After 14 quiet days"}],"signals":[{"at":"2026-11-11T18:17:56.000Z","source":"C41","sourceName":"Red Hat Security Data","role":"Vendor","severity":3,"title":"Red Hat: CVE-2026-123864 (important)","text":"nodejs: nodejs: Information disclosure via HTTPS parser re-entrancy","url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-123864.json"},{"at":"2026-11-11T19:17:32.790Z","source":"C6","sourceName":"NVD CVE API 2.0","role":"Database","severity":3,"title":"CVE-2026-123864 (CVSS 8.1)","text":"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…","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-123864"}],"crowd":[],"reference":{"nvd":{"published":"2026-11-11T19:17:32.790","score":8.1,"severity":"HIGH","desc":"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…","product":"","seen":1794435185345},"kev":null,"epss":null,"p0":false},"mergedInto":null,"publisher":"Event Monitor Cyber"}