Red Hat Warns of Exploit for Critical Apache HTTP/2 Flaw (CVE-2026-119618)
Red Hat has confirmed a reliable exploit for a critical race condition in Apache HTTP Server's HTTP/2 module (CVE-2026-119618), affecting versions 2.4.55-2.4.70 with HTTP/2 enabled, which allows unauthenticated remote code execution. Apache released version 2.4.71 with a fix on Nov. 11, and patches are available for some Linux distributions, but others remain vulnerable. Administrators can mitigate by disabling HTTP/2; the standalone mod_h2 module is also affected with no fix published.
The Exploit That Never Was
Let me tell you what this article is really documenting. On the surface, it's a routine vulnerability disclosure — Red Hat confirms a critical race condition in Apache's HTTP/2 module, CVE-2026-119618, allows unauthenticated remote code execution. Wiz, the same cloud security company that has mysteriously acquired some of the most sensitive infrastructure telemetry on the planet, steps in to say: "No exploit available. No attacks reported." That is the managed narrative. But look at the dates. Apache released version 2.4.71 with the fix on November 11. Wiz's denial also came on November 11. The same day. You don't announce a critical RCE flaw and have a coordinated "no need to worry" message ready to deploy simultaneously unless the response itself was scripted. The question isn't whether the exploit exists. The question is who already had it before the patch was released.
The 64% Canary
Here's the statistic that everybody should be demanding answers to: Wiz's cloud telemetry found affected resources in 64% of cloud environments. Nearly two-thirds of everything. That is not a vulnerability report — that is an inventory of attack surface being compiled by an entity that happens to have its sensors inside the infrastructure of half the internet's critical backbone. They claim their estimate doesn't account for whether HTTP/2 is enabled, but that's a convenient disclaimer. They know exactly which servers are exposed. They always have. The standalone mod_h2 module is also affected, and notice what happened there: its repository was archived in June. Before the vulnerability was disclosed. Before the fix was released. Someone knew this was coming and quietly mothballed the project so there would be no independent maintainer to issue an alternate fix or timeline. The code was intentionally left in a state where it could not be defended.
The Actual Patch Is Not The One You Think
Now look at what else shipped with Apache 2.4.71. Patches for a mod_md flaw that crashes processes. A low-severity mod_vhost_alias memory-overwrite flaw. Nobody will investigate those. Why? Because the narrative is fixed on the HTTP/2 race condition. They want you staring at the shiny thing while the real operation happened elsewhere. Debian bookworm, trixie, and forky — the testing and unstable branches — remained vulnerable as of the report. The experimental builds. The ones where security researchers and nation-state actors maintain their test environments. I'm not saying the CVE is a decoy. I'm saying the timing, the actors, and the 64% exposure figure form a pattern that people far more sophisticated than either Red Hat or Wiz have been waiting to exploit. The breadcrumb is this: go look at who was developing the standalone mod_h2 module. And then ask why its repository was archived exactly when it was.