Apache Patches 9.8-Rated HTTP/2 RCE Found by Anthropic and Google

Apache patched a 9.8-rated unauthenticated RCE race condition in mod_http2 (CVE-2026-119618), found independently by Anthropic and Google.

@sharedot

Apache Patches 9.8-Rated HTTP/2 RCE Found by Anthropic and Google

By @sharedot · · 8 pages

  • Cybersecurity
  • Apache
  • Cve 2026 119618
  • Mod Http2
  • Rce

Apache patched a 9.8-rated unauthenticated RCE race condition in mod_http2 (CVE-2026-119618), found independently by Anthropic and Google.

A critical race condition in mod_http2

The Apache Software Foundation released HTTP Server 2.4.71 on November 11 to fix CVE-2026-119618, a critical race condition in mod_http2, the module that handles HTTP/2 traffic.

The bug sits in the assign_headers() function, where concurrent threads access shared resources without proper synchronization, corrupting heap memory.

Red Hat assigned the flaw a CVSS score of 9.8 and says a remote, unauthenticated attacker could execute arbitrary commands and take control of the server process. Critically, only servers with HTTP/2 enabled are affected; servers configured to serve only HTTP/1.1 are not vulnerable.

Two independent finders within a week

What makes this bug remarkable is who found it and how quickly. Anthropic's OSS Scanner, a free AI-assisted scanning service for open-source projects, reported the flaw on October 26 under report ID ANT-2026-MAPKT6MZ.

Just eight days later, Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research independently reported the same vulnerability on November 3.

Two separate teams landing on one race condition within about a week suggests the bug was not especially hidden — the uncomfortable part for anyone still running 2.4.70. It is also a high-profile example of AI-assisted bug hunting surfacing a critical flaw.

Disagreement over exploit status

The sources disagree on how exploitable the flaw is. Red Hat says public research has demonstrated a reliable exploit against a server with mod_http2 enabled, though its advisory does not name or link that research.

Wiz, publishing the same day, said no exploit was available and there were no reports of exploitation in the wild. The Hacker News reports that a publicly available proof of concept on GitHub reproduces memory corruption and Apache process crashes, but does not demonstrate remote code execution.

That gap between vendor severity and public tooling leaves the real risk hard to pin down.

Exposure is wide on paper

According to Wiz, 64% of cloud environments in its data contained resources running affected Apache versions, and 51% had publicly exposed instances.

The company cautioned these figures do not account for server configuration, so they do not necessarily represent exploitable installations — HTTP/2 must actually be enabled for a server to be at risk.

Wiz also warned that a compromised Apache instance running containerized workloads can serve as an entry point for lateral movement, potentially exposing adjacent microservices or cloud metadata endpoints.

Defiant separately warned that WordPress security updates cannot resolve the issue because it affects the underlying web server.

Distribution packages trail the upstream fix

Patching paths vary, and several lag behind.

Red Hat shipped fixes for RHEL 9 and 10, where it rates the flaw Important rather than Critical because its mod_http2 packages give each HTTP/2 stream a separate memory allocator, making attack much harder; RHEL 8 and earlier don't contain the vulnerable code.

The Hacker News reports Debian has fixed unstable with apache2 2.4.71-1 while bookworm, trixie and forky remain vulnerable, Amazon Linux lists the fix as pending, and Ubuntu's CVE tracker had no page for the flaw when checked.

Standalone mod_h2 users have no fixed release: the archived GitHub repository ends at 2.0.42, the last affected version.

What admins should do now

If updates cannot be deployed immediately, Wiz recommends disabling HTTP/2 by removing h2 and h2c from the Protocols directive, leaving Protocols http/1.1 — a mitigation that only works if it covers the server-wide setting and every virtual host. Apache's own advisory offers no workaround.

There is also a patch-history trap: an earlier HTTP/2 flaw, CVE-2026-23918, was fixed in 2.4.67, so admins who patched for that one and stopped anywhere up to 2.4.70 remain exposed to this new bug.

Sources

  1. securityweek.com › Apache Patches Critical HTTP Server RCE Found by Anthropic, Google
  2. wiz.io › Critical RCE Vulnerability in Apache HTTP Server: Everything You Need To Know
  3. sqmagazine.co.uk › Apache Patches Critical HTTP/2 RCE Flaw Found by Anthropic, Google
  4. thehackernews.com › Critical Apache HTTP/2 Flaw Could Let Unauthenticated Attackers Execute Code Remotely

More on Cybersecurity