The Apache Software Foundation shipped httpd 2.4.71 on November 11, 2026 with a fix for CVE-2026-119618, a critical bug in the HTTP/2 module. An unauthenticated attacker who can reach a server that speaks HTTP/2 can corrupt heap memory and potentially run code as the web server user. Red Hat scores it CVSS 9.8. NVD hadn’t published a score when we checked.
Two teams found it separately: Anthropic’s OSS Scanner (reported October 26, tracked as ANT-2026-MAPKT6MZ) and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research (reported November 3).
Who is affected
- Apache HTTP Server 2.4.55 through 2.4.70, and only with HTTP/2 enabled, meaning
h2orh2cappears in aProtocolsdirective, server-wide or in any virtual host. Servers that serve only HTTP/1.1 aren’t vulnerable. - Standalone icing/mod_h2 2.0.8 through 2.0.42. That GitHub repo was archived in June 2026 and won’t get a fix. Move to the HTTP/2 module that ships with httpd.
- Trend Micro notes that RHEL 6, 7 and 8 aren’t affected, because their mod_http2 code is older than 2.0.8.
The exposure is large. Cyware’s November 12 briefing says 64% of cloud environments have vulnerable resources and 51% have publicly exposed instances.
How the bug works
assign_headers() builds the headers for each HTTP/2 stream. Streams run on worker threads, but connection-level state belongs to the connection thread. Both allocate from a shared, lock-free allocator without proper synchronization, so a worker can write into memory the connection thread owns.
The attacker controls the timing. One HTTP/2 connection can carry many simultaneous streams, so the race window can be made as wide as the attacker wants. When the race is won, the corruption hits neighbouring heap objects instead of crashing cleanly, and that’s how a denial-of-service bug becomes code execution. When it’s lost, a child process usually dies, which shows up in logs as instability rather than an attack. If you saw unexplained mod_http2 child crashes recently, look at them again.
What to do
# 1. Does the server negotiate HTTP/2? ("2" = exposed if unpatched)
curl -sS -o /dev/null --http2 -w '%{http_version}\n' https://your-host
# 2. Where is it enabled? Check server-wide AND per vhost
grep -R --include='*.conf' -n '^[[:space:]]*Protocols' /etc/apache2 /etc/httpd
# 3. Confirm the running version
httpd -v # or apache2 -v
- Upgrade to httpd 2.4.71 or your distro’s fixed package (RHEL 9/10: RHSA-2026:98981 and RHSA-2026:98978; Debian unstable: apache2 2.4.71-1), then restart, not just install.
- Can’t patch yet? Remove
h2andh2cfrom everyProtocolsline, leavingProtocols http/1.1, then reload and check again with curl. Apache doesn’t list any other workaround. - Rebuild images. Container images, AMIs and auto-scaling templates carry their own httpd binary. Reverse proxies and appliances built on httpd count too.
- Hunt. Look for bursts of concurrent HTTP/2 streams on one connection followed by child-process crashes, and for unexpected processes or new files owned by the httpd user.
WordPress and other app-level updates don’t help here. The bug is in the web server itself, so patch below the application.
The same release also fixes CVE-2026-106023 (important, a null pointer dereference in mod_md) and CVE-2026-109163 (low, a data overwrite in mod_vhost_alias).