A critical race‑condition bug in Apache HTTP Server’s HTTP/2 module (mod_http2) has been assigned CVE‑2026‑119618. The flaw allows an unauthenticated attacker to corrupt heap memory and potentially achieve remote code execution (RCE) on any server that has HTTP/2 enabled. The vulnerability was independently discovered by Anthropic’s OSS Scanner and Google Cloud’s Vulnerability Research team, and a patch was released on November 11, 2026 in Apache HTTP Server 2.4.71.
Key takeaways
- Only servers with HTTP/2 (h2 or h2c) enabled are vulnerable.
- The bug affects Apache HTTP Server 2.4.55‑2.4.70 and standalone mod_h2 2.0.8‑2.0.42.
- Patch to 2.4.71 or later, or disable HTTP/2, to eliminate the attack vector.
- Wiz reports 64% of cloud environments run vulnerable versions; 51% have publicly exposed instances.
- No public exploit is known yet, but a reliable proof‑of‑concept exists.
What the vulnerability does
The flaw resides in the assign_headers() function of the HTTP/2 module. When multiple threads process shared resources without proper synchronization, a race condition can corrupt heap memory. An attacker who can reach the server can trigger this corruption, leading to arbitrary code execution with the privileges of the web‑server process.
Who is affected
The vulnerability impacts any deployment that uses Apache HTTP Server’s HTTP/2 support. Specific version ranges are:
| Component | Affected Versions |
|---|---|
| Apache HTTP Server (mod_http2) | 2.4.55 – 2.4.70 |
| Standalone mod_h2 (GitHub) | 2.0.8 – 2.0.42 |
Red Hat Enterprise Linux (RHEL) ships its own packages; the fix is included in RHEL 9 and 10 as mod_http2‑2.0.26‑7.el9_9.1. Earlier RHEL releases (8 and below) do not contain the vulnerable code.
Why it matters
Apache HTTP Server powers a large share of the public web and countless cloud workloads. In cloud environments, a compromised Apache instance can become a foothold for lateral movement, exposing adjacent micro‑services or cloud metadata endpoints. With a CVSS score of 9.8/10, the flaw is considered critical and could give attackers full control of the server process.
Remediation steps
Security teams should act quickly:
- Upgrade Apache. Move to Apache HTTP Server 2.4.71 or later. This version includes a fix for the race condition.
- Update standalone modules. If you use the GitHub mod_h2 builds, upgrade to any version newer than 2.0.42 (no newer release exists yet; consider disabling the module).
- Disable HTTP/2 temporarily. If patching cannot be performed immediately, edit httpd.conf (or the relevant virtual‑host file) and remove h2 and h2c from the Protocols directive, leaving only http/1.1. # Restrict protocols to HTTP/1.1 Protocols http/1.1
- Validate configuration. Verify that the change applies to all virtual hosts, not just the server‑wide setting.
- Scan for vulnerable instances. Cloud‑security platforms (e.g., Wiz) provide queries to locate exposed Apache servers running affected versions.
What this means for you
If you manage web servers, containers, or virtual machines that run Apache with HTTP/2 enabled, you should check the version immediately. On Linux distributions, use the package manager to query the installed version (e.g., httpd -v or apache2 -v). For cloud‑hosted workloads, run a vulnerability scan focused on CVE‑2026‑119618.
Organizations that cannot patch within their change‑management windows can mitigate risk by disabling HTTP/2 until the upgrade is possible. Remember that WordPress or other CMS updates will not fix this issue; the underlying web server must be addressed.
What happens next
While no public exploit is confirmed in the wild, security researchers have demonstrated a reliable proof‑of‑concept that crashes the server and can lead to memory corruption. Expect additional advisory updates from Apache, Red Hat, Debian, Ubuntu, and other distributors as they roll out the patched packages. Keep an eye on vendor security bulletins and consider implementing automated patching for Apache components to reduce exposure to future zero‑day flaws.
How to stay protected
- Subscribe to security mailing lists for Apache, your OS distribution, and cloud providers.
- Integrate vulnerability scanning tools that include CVE‑2026‑119618 in their rule sets.
- Adopt a defense‑in‑depth approach: network segmentation, least‑privilege IAM roles, and regular log monitoring can limit the impact of a compromised web server.
Frequently asked questions
Which Apache versions are vulnerable to CVE-2026-119618?
Versions 2.4.55 through 2.4.70 of Apache HTTP Server with the HTTP/2 module enabled are vulnerable.
How can I quickly mitigate the Apache HTTP/2 flaw if I cannot patch right now?
Remove h2 and h2c from the Protocols directive in the Apache configuration, leaving only http/1.1, and restart the server.
What CVSS score does this vulnerability have?
The flaw is rated 9.8 out of 10, indicating a critical severity.
Do I need to update standalone mod_h2 builds?
Yes – any build older than version 2.0.42 is vulnerable; upgrade to a newer version or disable the module.
Is there an active exploit in the wild?
No public exploit has been reported yet, but a reliable proof‑of‑concept exists.
