Dev News Daily ENDE

HTTP/2 on patch day: Apache httpd and Node.js both shipped stream-handling fixes on 11 November

Two widely deployed servers published security releases on 11 November, and in both the largest risk sat in the same protocol layer. Apache httpd 2.4.71 fixes CVE-2026-119618, a critical race in mod_http2. Node.js 26.13.1, with matching releases for its two older LTS lines, fixes nine high-rated flaws, most of them in its http2 and tls modules.

The details differ, but the shape repeats. httpd's critical bug is about synchronisation: assign_headers() works on a resource shared between concurrent threads without proper locking, and the project says that can end in remote code execution (httpd security list). The Node.js fixes are about lifetime: headers released when a stream is removed, streams abandoned by nghttp2 detected, buffers and streams kept alive until pending socket writes complete (Node.js 26.13.1). In both cases the server holds state per stream that outlives a single request, and the bug is in who may touch that state, and when.

HTTP/2 multiplexes many streams over one connection, so a server tracks each stream, its headers, its buffered data and its flow-control accounting while others are in flight. Node.js has a separate medium-rated fix that charges data retained by streams to maxSessionMemory, which is the same bookkeeping viewed from the memory side.

TLS shows a related pattern in the Node.js release. Three changes stop a session's server name from shifting after the handshake, through resumption, renegotiation or a HelloRetryRequest. That is identity treated as state that must stay fixed for the life of a connection.

HTTP/2 on patch day: Apache httpd and Node.js both shipped stream-handling fixes on 11 November
HTTP/2 on patch day: Apache httpd and Node.js both shipped stream-handling fixes on 11 November — Dev News Daily

What operators can do now

The sources give concrete steps. For httpd, upgrade to 2.4.71; if that has to wait, Wiz's write-up suggests limiting Protocols to http/1.1, which takes mod_http2 out of the request path (Wiz). For Node.js, install the release for the line in use: 26.13.1, 24.22.3 or 22.23.5.

What to take from it

An inventory question follows from both: where in a stack is HTTP/2 actually terminated? A reverse proxy, an application server and a runtime may each speak it, and each carries its own per-stream state. Knowing which component does the work tells a team which of the two advisories, or both, applies to them.

Written by Victoria Shinder.