CVE
CVE-2026-123864, CVE-2026-123866, CVE-2026-123874, CVE-2026-123872, CVE-2026-123863, CVE-2026-123865, CVE-2026-126051, CVE-2026-123828, CVE-2026-123867, CVE-2026-123868, CVE-2026-123871, CVE-2026-123875, CVE-2026-123877, CVE-2026-123829, CVE-2026-123862, CVE-2026-106071, CVE-2026-123873, CVE-2026-119618, CVE-2026-106023, CVE-2026-109163, CVE-2026-121737, CVE-2026-119236, CVE-2026-119233, CVE-2026-119234, CVE-2026-119235, CVE-2026-119237, CVE-2026-119723
CWE
CWE-416, CWE-125, CWE-362, CWE-787, CWE-287, CWE-295, CWE-400, CWE-476, CWE-617
Affected Surface
- Node.js runtime `22.x < 22.23.5`, `24.x < 24.22.3`, and `26.x < 26.13.1` (and all End-of-Life release lines) (`CVE-2026-123864`, `CVE-2026-123866`, `CVE-2026-123874`, `CVE-2026-123872`, `CVE-2026-123863`, `CVE-2026-123865`, `CVE-2026-126051`, `CVE-2026-123828`, `CVE-2026-123867`, `CVE-2026-123868`, `CVE-2026-123871`, `CVE-2026-123875`, `CVE-2026-123877`, `CVE-2026-123829`, `CVE-2026-123862`, `CVE-2026-106071`, and `CVE-2026-123873`, plus bundled `llhttp 9.4.4`, `undici 8.12.4`, `sqlite 3.54.1`, and `brotli 1.2.1`)
- Apache HTTP Server (`httpd`) versions `2.4.55` through `2.4.70` and `icing/mod_h2` versions `2.0.8` through `2.0.42` (`CVE-2026-119618` Critical `mod_http2` RCE, fixed in `httpd 2.4.71`), `httpd` `2.4.30` through `2.4.70` (`CVE-2026-106023` Important `mod_md` NULL pointer dereference), and `httpd` `2.4.69` through `2.4.70` (`CVE-2026-109163` `mod_vhost_alias` stack overwrite)
- Meta `proxygen` and `mvfst` versions `< v2026.11.09.00` (`CVE-2026-121737` HTTP/1.1 pipelined stream use-after-free, `CVE-2026-119236` QUIC Handshake `CRYPTO` frame memory exhaustion, and `CVE-2026-119233`, `119234`, `119235`, `119237`) and `HHVM` prior to commit `23c061f4e804` (`CVE-2026-119723` query/form nested-array crash)
TL;DR
On 11 November 2026 (12:19 to 17:19 UTC), the Node.js project, the Apache HTTP Server team, and Meta disclosed 26 vulnerabilities across HTTP/1.1, HTTP/2, HTTP/3, and TLS server implementations:
- Node.js
26.13.1,24.22.3, and22.23.5patch 16 CVEs (including 7 High-severity HTTP/2 and TLS flaws):- Cross-connection heap and private-key disclosure in HTTPS (
CVE-2026-123864, High,22.x/24.x/26.x) and HTTP/2 (CVE-2026-123866, High,22.x/24.x/26.x): Insrc/crypto/crypto_tls.cc, callingTLSWrap::DoWrite()with a zero-length buffer invokedClearOut()synchronously even when called from JavaScript executing insidellhttp’son_bodycallback.ClearOut()decrypted the next TLS record and re-enteredllhttp_execute()while the outer parser frame was still mid-body, triggering a use-after-free and out-of-bounds heap read that copied other connections’ memory (including TLS private keys and other users’ requests) into the current request body (CVE-2026-123864, commit940cae5c3346). Insrc/node_http2.cc(CVE-2026-123866, commit7df134e2ceaf), tearing down an HTTP/2 stream while a socket write was backpressured freed the stream’s response buffer whileoutgoing_buffers_still held a raw slice pointer (uv_buf_init), writing freed heap memory (including other connections’ response buffers) directly to the peer socket. - HTTP/2
respondWithFile()use-after-free (CVE-2026-123874, High,24.x/26.x),session.altsvc()1-byte heap overflow (CVE-2026-123828, Medium), and remote process aborts (CVE-2026-123863High,CVE-2026-123865High,CVE-2026-126051High,CVE-2026-123875Medium): Resetting astream.respondWithFile()orstream.respondWithFD()stream while a partial write slice was queued on the socket freed theHttp2Stream(req_wrapwasnullptron non-final slices), causing the write-completion callback to make a virtual call through a freedHttp2Stream(CVE-2026-123874, commit9183db64fe78). Meanwhile, removing a stream fromstreams_without callingClearHeaders()trippedCHECK_EQ(current_nghttp2_memory_, 0)in~Http2Session()(CVE-2026-123863, incomplete fix forCVE-2024-27983), triggering a protocol error afterGOAWAY(NO_ERROR)leaked sessions inCLOSE_WAIT(CVE-2026-123865, incomplete fix forCVE-2026-48937), and passing a long:authorityheader tosession.altsvc()wrote a null byte 1 byte past theMaybeStackBuffer<uint8_t>allocation (CVE-2026-123828). - Per-host mTLS and
https.Agentcertificate-validation bypasses (CVE-2026-123872High,CVE-2026-123867Medium, andCVE-2026-123877Medium): Clients could switch the SNIservernameduring TLS 1.2 renegotiation, TLS 1.3HelloRetryRequest, or session resumption to carry a client certificate validated under a permissive host onto a stricter protected host (CVE-2026-123872);server.addContext(host, { ca })silently kept the default client CA whenever the SNI context omitted a server certificate (CVE-2026-123867); andhttps.Agent.prototype.getName()produced the same session-cache key for{ ca: [] }and an omittedcaoption (CVE-2026-123877).
- Cross-connection heap and private-key disclosure in HTTPS (
- Apache HTTP Server
2.4.71(CVE-2026-119618Critical RCE,CVE-2026-106023Important,CVE-2026-109163Low): Inmodules/http2/h2_request.c(2.4.55through2.4.70andicing/mod_h22.0.8through2.0.42), when an HTTP/2 request carried aContent-Typeheader and ended immediately withEND_STREAM(eos) and noContent-Length,assign_headers()calledapr_table_setn(req->headers, "Content-Length", "0")on the sharedconst h2_request *reqstructure rather than the per-requestr->headers_intable (commit824beab9b942). Becauseapr_table_tis not thread-safe and backed by the connection/stream pool, concurrent access corrupted the APR pool/heap and enabled remote code execution. - Meta
proxygen&mvfstv2026.11.09.00(CVE-2026-121737,CVE-2026-119233to119237) andHHVM(CVE-2026-119723):proxygenfreed a pipelined HTTP/1.1 stream during write-timeout reset and then continued using it (CVE-2026-121737),mvfstretained uncountedHandshake-levelCRYPTOframes when a client withheldHANDSHAKE_DONEACKs (CVE-2026-119236), andHHVMdereferenced an uncreated nested array whensymtable->append()failed during query/form parameter parsing (CVE-2026-119723).
What to do now: Upgrade Node.js to 26.13.1, 24.22.3, or 22.23.5; upgrade Apache HTTP Server to 2.4.71 (or patch mod_http2 / mod_h2 with 824beab9b942); and update Meta proxygen and mvfst to >= v2026.11.09.00 and HHVM past commit 23c061f4e804.
Affected runtimes and servers
| Ecosystem | Product / Package | CVE IDs | Severity | Affected versions | Fixed version |
|---|---|---|---|---|---|
| Node.js | node (https, http2, tls, zlib, Permission Model) | CVE-2026-123864, CVE-2026-123866, CVE-2026-123872, CVE-2026-123865, CVE-2026-123867, CVE-2026-123871, CVE-2026-123875, CVE-2026-123877, CVE-2026-123829, CVE-2026-123862, CVE-2026-106071 | High / Medium / Low | 22.x < 22.23.5, 24.x < 24.22.3, 26.x < 26.13.1 | 22.23.5, 24.22.3, 26.13.1 |
| Node.js | node (http2, tls, v8.writeHeapSnapshot) | CVE-2026-123874, CVE-2026-123863, CVE-2026-126051, CVE-2026-123828, CVE-2026-123868, CVE-2026-123873 | High / Medium / Low | 24.x < 24.22.3, 26.x < 26.13.1 | 24.22.3, 26.13.1 |
| C / Web Server | Apache HTTP Server (httpd) & icing/mod_h2 | CVE-2026-119618 (Critical RCE), CVE-2026-106023 (Important), CVE-2026-109163 (Low) | Critical / Important / Low | httpd 2.4.55..2.4.70 (119618), 2.4.30..2.4.70 (106023), 2.4.69..2.4.70 (109163); mod_h2 2.0.8..2.0.42 | httpd 2.4.71 (commits 824beab9b942, 1b47e95c61fb) |
| C++ / HTTP & QUIC | Meta proxygen and mvfst | CVE-2026-121737, CVE-2026-119233, CVE-2026-119234, CVE-2026-119235, CVE-2026-119236, CVE-2026-119237 | High / Medium | < v2026.11.09.00 | v2026.11.09.00 (daf245bba7fe, 7e5cff58e8cb) |
| C++ / Runtime | Meta HHVM | CVE-2026-119723 | High (Pre-app remote crash DoS) | < 23c061f4e804 | Commit 23c061f4e804 |
Technical analysis
1. Node.js CVE-2026-123864: how a zero-length TLS write inside on_body re-enters llhttp_execute() and leaks heap memory
In Node.js HTTPS servers, incoming ciphertext is decrypted by TLSWrap::Cycle() (ClearOut()), which emits plaintext chunks to the attached HTTP parser listener (Parser::OnStreamRead -> Parser::Execute -> llhttp_execute()). While llhttp_execute() is parsing an HTTP request body, it invokes the on_body callback (Parser::OnBody), which synchronously runs JavaScript data listeners on the IncomingMessage stream.
In src/crypto/crypto_tls.cc prior to commit 940cae5c3346, TLSWrap::DoWrite() contained a special case for zero-byte writes (length == 0) that called ClearOut() directly without checking whether TLSWrap was already inside Cycle():
--- a/src/crypto/crypto_tls.cc
+++ b/src/crypto/crypto_tls.cc
@@ -1123,7 +1123,11 @@ int TLSWrap::DoWrite(WriteWrap* w,
// WriteWrap was accepted by the stream, or that we call Done() on it.
if (length == 0) {
Debug(this, "Empty write");
- ClearOut();
+ // When the write comes from JS running inside Cycle(), for example from a
+ // stream listener in ClearOut(), the cycle reads and encrypts any pending
+ // data once that JS returns. Reading here would hand the next record to
+ // the listener while it is still processing the current one.
+ if (cycle_depth_ == 0) ClearOut();
if (BIO_pending(enc_out_) == 0) {
Meanwhile, in src/node_http_parser.cc, Parser::Execute() and Parser::OnStreamRead() overwrote current_buffer_data_ and current_buffer_len_ with nullptr and 0 on exit rather than restoring the outer frame’s buffer pointer:
- An HTTPS handler calls
res.flushHeaders()before the request body finishes, and later callsres.end(chunk)inside a body data listener (which triggers a zero-length TLS write alongside the chunk). TLSWrap::DoWrite()seeslength == 0and callsClearOut()while the outerllhttp_execute()call is still paused insideon_body.ClearOut()decrypts the next queued TLS record and callsParser::OnStreamRead(), which re-entersllhttp_execute()on the new buffer and then setscurrent_buffer_data_ = nullptrwhen the inner call returns.- When execution unwinds back to the outer
llhttp_execute()frame, pointer arithmetic between the outer buffer andcurrent_buffer_data_reads freed or unrelated heap memory (including TLS private keys and other clients’ HTTP requests) and appends it to the caller’s request body.
Commit 940cae5c3346 skips ClearOut() when cycle_depth_ > 0, saves and restores outer_data and outer_len across nested Parser calls, and aborts parsing with HPE_REENTRANT_EXECUTE if a callback pointer no longer lies within current_buffer_data_.
2. Node.js HTTP/2 use-after-free flaws (CVE-2026-123866 and CVE-2026-123874) and TLS SNI mTLS bypasses (CVE-2026-123872, CVE-2026-123867, CVE-2026-123877)
Two High-severity use-after-free bugs in src/node_http2.cc stemmed from how Http2Session::OnSendData() sliced partial stream writes into outgoing_buffers_:
--- a/src/node_http2.cc
+++ b/src/node_http2.cc
@@ -2173,15 +2173,19 @@ int Http2Session::OnSendData(
if (write.buf.len <= length) {
// This write does not suffice by itself, so we can consume it completely.
length -= write.buf.len;
+ write.stream = stream;
session->PushOutgoingBuffer(std::move(write));
stream->queue_.pop();
continue;
}
// Slice off `length` bytes of the first write in the queue. Retain the
// originating request until the slice is no longer used by the socket.
- session->PushOutgoingBuffer(
- NgHttp2StreamWrite { uv_buf_init(write.buf.base, length) });
+ session->PushOutgoingBuffer(
+ NgHttp2StreamWrite{nullptr,
+ write.buffer_owner,
+ stream,
+ uv_buf_init(write.buf.base, length)});
write.buf.base += length;
write.buf.len -= length;
break;
@@ -2279,8 +2283,7 @@ void Http2Session::OnStreamRead(ssize_t nread, const uv_buf_t& buf_) {
bool Http2Session::HasWritesOnSocketForStream(Http2Stream* stream) {
for (const NgHttp2StreamWrite& wr : outgoing_buffers_) {
- if (wr.req_wrap && WriteWrap::FromObject(wr.req_wrap)->stream() == stream)
- return true;
+ if (wr.stream.get() == stream) return true;
}
return false;
}
- Response heap memory leaked to peer (
CVE-2026-123866, commit7df134e2ceaf): InHttp2Stream::DoWrite(),req_wrapwas attached only to the last buffer entry (i == nbufs - 1), and partial slices created inOnSendData()hadreq_wrap = nullptr. When a stream was reset (RST_STREAMor stream timeout) while a partial slice sat inoutgoing_buffers_, the underlying buffer was freed before the TCP socket finished transmitting the slice, sending freed heap memory (including other connections’ responses) over the wire. Http2Streamuse-after-free onrespondWithFile()(CVE-2026-123874, commit9183db64fe78):HasWritesOnSocketForStream()checkedwr.req_wrap && WriteWrap::FromObject(wr.req_wrap)->stream() == stream. Because partial slices hadwr.req_wrap == nullptr,HasWritesOnSocketForStream()returnedfalsewhile a slice was still queued on the socket, allowingHttp2Streamto be freed and later dereferenced via a virtual call when the write completed.- Per-host mTLS and
https.Agentbypasses (CVE-2026-123872,CVE-2026-123867,CVE-2026-123877): Commits97b1357f0843,e750e1fa0258, anda8d62869496f(CVE-2026-123872) bind TLS session IDs to the SNIservername, reject SNI changes during TLS 1.2 renegotiation or TLS 1.3HelloRetryRequest, and disable resumption for mTLS servers without asessionIdContext. Commit66e72ec604b2(CVE-2026-123867) ensuresTLSWrap::CertCbDone()callsw->SetCACerts(sc)even when anaddContext(host, { ca })SNI context has no separate server certificate. And commitfa61009dc1fa(CVE-2026-123877) replaces string concatenation inhttps.Agent.prototype.getName()with typed, length-prefixedgetTlsOptionKey()encoding soca: [](which encodes as'a0') no longer collides withca: undefined('').
3. Apache HTTP Server 2.4.71 (CVE-2026-119618): mod_http2 assign_headers() shared-table race to RCE
In Apache HTTP Server 2.4.55 through 2.4.70 (and icing/mod_h2 2.0.8 through 2.0.42), when an HTTP/2 stream is dispatched to a worker thread, h2_request_copy() creates the Apache request_rec *r and calls assign_headers(r, req, ...) in modules/http2/h2_request.c.
When a request carried a Content-Type header, omitted Content-Length, and set END_STREAM (req->eoh with no body), line 353 wrote "Content-Length": "0" into req->headers instead of r->headers_in:
--- a/modules/http2/h2_request.c
+++ b/modules/http2/h2_request.c
@@ -350,7 +350,7 @@ static void assign_headers(request_rec *r, const h2_request *req,
/* If we have a content-type, but already seen eos, no more
* data will come. Signal a zero content length explicitly.
*/
- apr_table_setn(req->headers, "Content-Length", "0");
+ apr_table_setn(r->headers_in, "Content-Length", "0");
}
}
Although req is declared const h2_request *req, req->headers is a non-const apr_table_t * allocated from the h2_mplx / stream pool on the main connection thread. Calling apr_table_setn(req->headers, ...) on the worker thread mutated req->headers (and triggered apr_array_push reallocations from the underlying apr_pool_t) concurrently with HTTP/2 multiplexer operations on the connection thread, causing heap corruption and remote code execution (commit 824beab9b942, found independently by Anthropic’s OSS Scanner ANT-2026-MAPKT6MZ and Anthony Weems & Simon Scannell of Google Cloud Vulnerability Research).
Detection and remediation
# 1. Check running Node.js and Apache HTTP Server versions
node -v 2>/dev/null || true
httpd -v 2>/dev/null || apache2 -v 2>/dev/null || true
# 2. Search Dockerfiles, CI workflows, and package manifests for vulnerable Node.js or httpd images
rg -n 'FROM\s+node:|node-version|httpd:2\.4\.' Dockerfile* .github/workflows/*.yml 2>/dev/null
# 3. Audit Node.js codebases for the high-risk HTTP/2 and mTLS patterns affected by CVE-2026-123864 / 123874 / 123867 / 123828
rg -n 'respondWithFile|respondWithFD|flushHeaders|addContext\s*\(|\.altsvc\s*\(' --glob '*.{js,ts,mjs,cjs}' 2>/dev/null
- Upgrade Node.js to
26.13.1,24.22.3, or22.23.5: If you run HTTPS servers that callres.flushHeaders()(CVE-2026-123864) or HTTP/2 servers that stream responses (CVE-2026-123866), treat exposed TLS private keys or session tokens in process memory as potentially disclosed and rotate them after upgrading. - Upgrade Apache HTTP Server to
2.4.71: On servers where2.4.71cannot be deployed immediately and HTTP/2 is enabled (Protocols h2 h2c http/1.1), removeh2/h2cfromProtocolsor disablemod_http2until patched. - Update Meta
proxygenandmvfstto>= v2026.11.09.00andHHVMpast commit23c061f4e804.
Timeline
- 2026-09-29 to 2026-11-03: Researchers report
CVE-2026-106023,CVE-2026-109163, andCVE-2026-119618to the Apache HTTP Server security team. - 2026-11-04: Node.js publishes its November 2026 security release pre-alert on
oss-security. - 2026-11-11 (
12:19to15:17 UTC): Apache HTTP Server releases2.4.71and publishesCVE-2026-119618(Criticalmod_http2RCE),CVE-2026-106023(mod_md), andCVE-2026-109163(mod_vhost_alias) onoss-securityand NVD. - 2026-11-11 (
16:44to17:19 UTC): Node.js tags and publishesv26.13.1,v24.22.3, andv22.23.5fixing 16 CVEs (CVE-2026-123863throughCVE-2026-126051), and NVD publishes the Metaproxygen,mvfst, andHHVMadvisories (CVE-2026-121737,CVE-2026-119233to119237,CVE-2026-119723).
From research to remediation
Check whether this pattern exists in your codebase
Turn this research into a remediation workflow. Use AI-native static analysis to find similar application vulnerabilities and generate review-ready fixes.
References
- Node.js Security Releases (11 November 2026): v26.13.1, v24.22.3, and v22.23.5 (CVE-2026-123863 through CVE-2026-126051)
- nodejs/node v26.13.1 release commit e9c277643b02 and fix commits 940cae5c3346 (CVE-2026-123864), 7df134e2ceaf (CVE-2026-123866), 9183db64fe78 (CVE-2026-123874), and 97b1357f0843 (CVE-2026-123872)
- Apache HTTP Server 2.4.71 Security Advisories (CVE-2026-119618 mod_http2 RCE, CVE-2026-106023 mod_md, CVE-2026-109163 mod_vhost_alias) and commit 824beab9b942
- oss-security (11 November 2026): CVE-2026-119618 Apache HTTP Server mod_http2 heap corruption and RCE in assign_headers
- Meta proxygen commit daf245bba7fe (CVE-2026-121737), mvfst commit 7e5cff58e8cb (CVE-2026-119236), and HHVM commit 23c061f4e804 (CVE-2026-119723)