The short version
- The flaw. CVE-2026-119618 is a race condition in mod_http2, the module that handles HTTP/2 traffic, and can corrupt server memory. Apache HTTP Server versions 2.4.55 through 2.4.70 are affected; version 2.4.71, released on 11 November, fixes it.
- Exploit status. Red Hat says public research has demonstrated a reliable exploit against a default server with mod_http2 enabled, but does not name that research. Wiz said when its analysis was published on 11 November that no exploit was available and no in-the-wild attacks had been reported; a GitHub proof of concept reports reproducing crashes but not remote code execution.
- Exposure. Wiz reports that 64% of cloud environments in its data held resources running affected Apache versions and 51% had publicly exposed instances, though the figures ignore configuration. Only servers with HTTP/2 switched on are vulnerable.
- Standalone module. Separate builds of the module, published on GitHub as mod_h2 from 2.0.8 to 2.0.42, are affected and have no fixed release. The repository has been read-only since it was archived on 9 June.
Timeline
| Date | Event |
|---|---|
| 26 October | Anthropic's OSS Scanner, a free scanning service for open-source projects, reports the flaw. |
| 3 November | Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research independently report the same flaw. |
| 11 November | Apache releases version 2.4.71, and Red Hat ships fixed mod_http2 packages for Red Hat Enterprise Linux 9 and 10. |
| 12 November | News reports describe vulnerable and internet-reachable servers, and Wiz's analysis is widely cited. |
The vulnerability and the patch
The flaw sits in assign_headers() in mod_http2, where concurrent threads share resources without proper synchronisation. Apache describes this as a concurrent execution problem that can lead to remote code execution. An attacker who can reach the server needs no credentials, and any code runs with the privileges of the web server process.
Version 2.4.71 also fixes a null pointer dereference in mod_md that can crash the server process and a low-severity data overwrite in mod_vhost_alias. Distributions ship their own builds with their own package numbers, so administrators should follow their vendor's advisory rather than the upstream version string alone. The Apache advisory offers no workaround.
Who is affected
HTTP/2 runs only where the Protocols directive turns it on, using h2 for HTTP/2 over TLS and h2c for HTTP/2 over plain TCP. The setting can apply server-wide or to a single virtual host, so administrators should check both. BleepingComputer reports that HTTP/2 is off by default; Red Hat says servers serving only HTTP/1.1 are not vulnerable.
Wiz's figures describe versions present in cloud environments, not confirmed exploitable hosts, because configuration is not counted. Researchers at watchTowr confirmed that HTTP/2 must be enabled and advised administrators to "patch now or drop h2 until you can." Defiant warned that WordPress security updates cannot resolve the issue, since it affects the underlying web server.
Distribution status and disagreement
Red Hat rates the flaw Important rather than Critical on Red Hat Enterprise Linux 9 and 10, because its mod_http2 packages give each HTTP/2 stream its own memory allocator, which the vendor says makes an attack much harder. Releases 6, 7 and 8 do not contain the vulnerable code. Red Hat JBoss Core Services and Red Hat Hardened Images are listed as affected with no fix.
Debian unstable is fixed; bookworm, trixie and forky are listed as vulnerable with no fix named. Amazon Linux 2, 2023 and the 2027 preview are listed as awaiting a fix. The Hacker News found no Ubuntu CVE page for the flaw when it checked. The two accounts of exploitability differ: Red Hat points to demonstrated public research, while Wiz saw no working exploit at publication.
What is not known yet
- What public research Red Hat refers to as demonstrating a reliable exploit, and whether that exploit works against unmodified upstream builds.
- Whether anyone has attempted exploitation since 11 November, given that Wiz's assessment predates wider publication.
- How many internet-facing servers actually run with HTTP/2 enabled, since the exposure percentages ignore configuration.
- Whether a fixed standalone mod_h2 release will appear, given that the repository is archived.
- Which Ubuntu releases carry the vulnerable code and when a fix will be published.
What to do
If you run Apache HTTP Server
- Upgrade upstream builds to 2.4.71.
- Check the Protocols directive server-wide and in every virtual host, then remove h2 and h2c so only http/1.1 remains if you cannot patch yet.
- Apply the same Protocols change to any server using standalone mod_h2 builds from 2.0.8 to 2.0.42, for which no fixed release exists.
If you use a distribution build
- Install the fixed mod_http2 package named in your vendor's advisory; on Red Hat Enterprise Linux 9 the fix ships as mod_http2-2.0.26-7.el9_9.1.
- Check the status of Debian bookworm, trixie and forky, Amazon Linux and Ubuntu, which the sources list as vulnerable or without a fix at the time of writing.
- Mark Red Hat JBoss Core Services and Hardened Images as affected with no fix listed and watch for updates.
For everyone else
- Inventory internet-facing web servers and confirm which have HTTP/2 enabled before assuming exposure figures apply to you.
- Do not rely on content management system or plugin updates to close this flaw; it is fixed at the web server layer.
- Treat a server crash or unexpected process restart on an affected host as worth investigating while proof-of-concept code circulates.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.