Apache mod_http2 CVE-2026-119618: how an HTTP/2 race condition becomes RCE
In Apache HTTP Server 2.4.55–2.4.70, mod_http2 can corrupt the heap via a race in shared header table handling, potentially enabling remote code execution. Fixed in 2.4.71.

Apache HTTP Server is one of the internet’s invisible workhorses. Even behind CDNs or reverse proxies, httpd still runs in countless backends. The 2.4.71 release published on November 11, 2026 patches a critical issue in its HTTP/2 module: CVE-2026-119618.
Apache rates the issue as critical. Red Hat assigns a 9.8 CVSS 3.1 score. The affected range is broad: 2.4.55 through 2.4.70. On servers with HTTP/2 enabled, the flaw can lead to heap corruption and potentially remote code execution (RCE) without authentication.
This post explains the technical mechanism, which deployments are actually at risk, and what you can do beyond upgrading.
Quick summary
| Field | Value |
|---|---|
| CVE | CVE-2026-119618 |
| Severity | Critical (Apache), CVSS 9.8 (Red Hat) |
| Affected | 2.4.55–2.4.70 with mod_http2/HTTP/2 enabled |
| Fixed | 2.4.71 |
| Impact | Heap corruption, potential unauthenticated RCE |
What’s going wrong (high level)
HTTP/2 uses HPACK header compression with dynamic tables shared across streams/connections in ways that require careful synchronization. A race condition in mod_http2’s handling of shared header table state can allow concurrent operations to observe or mutate inconsistent state. That inconsistency can translate into memory safety violations (heap corruption) under attacker-controlled timing/inputs.
You don’t need valid credentials—just the ability to speak HTTP/2 to a vulnerable endpoint and trigger the relevant code paths.
Am I affected?
- Yes, likely: You run Apache 2.4.55–2.4.70 and serve HTTP/2 (
Protocols h2 ...,mod_http2loaded) directly to clients or untrusted networks. - Maybe: You terminate HTTP/2 at a CDN/proxy but also expose origin httpd with HTTP/2 to other paths.
- Less exposed: HTTP/2 disabled (
h2off) or versions outside the range.
Check: httpd -v / apache2 -v, loaded modules, and Protocols configuration.
Mitigation and fix
- Upgrade to 2.4.71 (or vendor-patched builds) — the definitive fix.
- Temporary workaround: Disable HTTP/2 (
Protocols http/1.1) if you cannot patch immediately (with performance/feature tradeoffs). - Reduce exposure: Restrict access to vulnerable endpoints, WAF/rate-limit where applicable (not a substitute for patching).
Takeaway
Protocol parsing and compression code is a frequent source of memory-safety bugs, and concurrency makes them worse. Treat HTTP/2-facing servers as high-priority patch targets when a critical mod_http2 CVE drops.