Apache Patches Critical HTTP/2 Remote Code Execution Flaw
The Apache Software Foundation has fixed a critical HTTP/2 vulnerability tracked as CVE-2026-119618 in Apache HTTP Server 2.4.71, released on . The flaw can let a remote attacker run code on the server with the privileges of the web server process, and no authentication is required.

Anthropic’s OSS Scanner and Google Cloud’s Vulnerability Research teams discovered the bug. Red Hat rates it CVSS 9.8 (Critical). Cloud security firm Wiz says a significant portion of exposed Apache instances remain vulnerable, though only servers with HTTP/2 enabled are affected.

The affected versions are:

  • Apache HTTP Server 2.4.55 through 2.4.70
  • Standalone mod_h2 2.0.8 through 2.0.42

A Race Condition in Shared Header Memory

The problem sits in mod_http2, the module that serves many concurrent HTTP/2 streams over a single connection and spreads request processing across worker threads. When a request comes in, the code clones a shared header table (req->headers) into the per-request headers_in structure. It then writes to the shared table without adequate synchronization.

Because the threads run in an unpredictable order, that is a race condition, and depending on timing it can corrupt heap memory. Uncontrolled heap corruption usually just crashes a worker process. Skilled attackers, though, can groom the heap layout to overwrite critical memory pointers and turn the crash into arbitrary remote code execution.

That is not only a theoretical risk. Public technical analysis released shortly after disclosure demonstrated reliable exploitation against default-configured servers using the event MPM with mod_http2 enabled.

Two Ways to Fix It, and Only One Is a Patch

The Apache advisory publishes no workaround for CVE-2026-119618, so administrators have two options. They can upgrade to Apache HTTP Server 2.4.71 or an appropriately patched vendor package, or they can remove h2 and h2c from the Protocols directive to turn HTTP/2 off.

Scope is wider than public-facing websites. Any Apache instance reachable from an untrusted network with HTTP/2 enabled is affected, including internal reverse proxies and appliance management interfaces.

For now, the flaw is not listed in the CISA Known Exploited Vulnerabilities catalog, and there are no public reports of exploitation in the wild. Version 2.4.71 also fixes two other vulnerabilities, including CVE-2026-106023, a null pointer dereference in mod_md that crashes a child process during HTTP request handling.

Hashlytics Take

The absence from the CISA catalog is the least reassuring part of this story. A public write-up showing reliable exploitation against default configurations means the hard work has already been done for anyone who wants to try, and that gap between a published technique and a “known exploited” listing is usually when scanning starts. The servers most likely to linger are the ones nobody thinks of as web servers: reverse proxies and appliance management interfaces that ship Apache inside a vendor package. Those only get fixed when the vendor ships an update, so checking which of your own systems quietly run HTTP/2 on Apache is worth doing before the patch itself.

Follow Hashlytics on Bluesky, Facebook, LinkedIn , Telegram and X to Get Instant Updates