Singapore’s Cyber Security Agency (CSA) warned in mid-November that attackers are exploiting CVE-2026-119618, a race-condition flaw in the Apache HTTP Server’s mod_http2 module, and that a proof-of-concept exploit is public. The bug allows remote code execution without a login.
CSA Alert AL-2026-164 Confirms Exploitation of the mod_http2 Flaw
The CSA’s alert, numbered AL-2026-164, moves the vulnerability from a patched bug to an actively exploited one. Apache’s 2.4.71 release in mid-November carried the fix, and this article covers the new development: exploitation and the public proof of concept.
Exploitation Rose After the One-Line Fix Became Public
Wiz says it saw no live attacks at first. Activity jumped after the one-line fix became public, an example of attackers studying a small patch to work out the underlying weakness.
The CSA alert page lists the alert date as November 17. In its wording, the flaw is being exploited and a public exploit is in circulation, and “users and administrators of affected products are advised to update to the latest versions immediately.”
Anthropic’s OSS Scanner and Google Cloud Researchers Reported the Flaw Separately
Anthropic’s OSS Scanner reported the flaw on October 26 under the identifier ANT-2026-MAPKT6MZ. Google Cloud Vulnerability Research, through Anthony Weems and Simon Scannell, reported it on November 3. The Cloud Security Alliance Labs describes the fix as shipping 16 days after the first report.
How the assign_headers() Race Condition Leads to RCE
The flaw is a race condition (CWE-362) in the assign_headers() function of mod_http2. Threads share a lock-free memory pool without proper locking, which allows heap corruption and remote code execution as the web server user, with no login required. Only servers that have mod_http2 enabled are affected.
Apache httpd Versions and Distributions Affected by mod_http2
The flaw affects Apache HTTP Server 2.4.55 through 2.4.70 with mod_http2, and standalone mod_h2 versions 2.0.8 through 2.0.42. Ubuntu 22.04 and 20.04 LTS and Red Hat Enterprise Linux 9 and 10 are also affected.
Anthropic and Google Cloud Teams Found the Bug Independently
The vulnerability was found independently by teams at Anthropic and Google Cloud. Severity scores differ: the CSA and CISA rate it 8.1, while Red Hat and Amazon rate it 9.8.
Wiz Data Shows a Large Exposed Footprint
Wiz data shows that 64 percent of cloud environments hold vulnerable assets and 51 percent expose them publicly. That footprint, combined with unauthenticated remote code execution and a public exploit, explains the urgency of the CSA warning.
The standalone mod_h2 project on GitHub was archived in June with no patch. Users of that standalone module therefore have no upstream fix to apply.
Debian and Red Hat Patch Status for the mod_http2 Flaw
As of November 12, per Cloud Security Alliance Labs, Debian trixie and sid were fixed under DSA-6620-1. Debian bookworm was still listed vulnerable despite a 2.4.71-1 package, and forky was vulnerable. RHEL 9 and 10 had no errata yet and are rated “Important” rather than Critical because the separate allocator “substantially increases the complexity of exploiting the flaw.” RHEL 8 and earlier are not affected, since their packages predate the vulnerable mod_http2 2.0.8 code. No Ubuntu advisory had been identified at that time, and this status may have changed.
Patch and Mitigation Options for CVE-2026-119618
Administrators should update to Apache 2.4.71 or to patches from their operating system vendors, then restart httpd and rebuild container images so that stale images do not keep the vulnerable module. Where patching is not possible, setting Protocols to http/1.1 disables HTTP/2 and removes the mod_http2 attack path.
The container step matters because a patched host can still run vulnerable workloads if images were built before the fix. Teams that use the standalone mod_h2 module need to consider moving off it, given that it is archived and unpatched.
For servers without fixed packages, administrators can also unload mod_http2, provided no gRPC or HTTP/2-dependent services exist.
