Critical Apache HTTP Server RCE Vulnerability Under Active Exploitation

Apache has patched a critical remote code execution (RCE) vulnerability affecting its HTTP/2 module, mod_http2. Tracked as CVE-2026-119618, this zero-authentication flaw can allow attackers to execute arbitrary commands on vulnerable servers. Administrators are urged to update to the fixed version immediately.

What’s going on

The flaw lies in the assign_headers function of mod_http2, which fails to properly manage shared resources in multi-threaded environments. The bug creates a race condition that can corrupt the server’s heap memory. Attackers exploiting this corruption can gain RCE privileges with the same permissions as the Apache process. Low-protocol settings like HTTP/1.1 aren’t affected—only setups where HTTP/2 or the standalone mod_h2 (versions 2.0.8 through 2.0.42) are enabled are at risk.

Severity, exploitation & affected installs

This issue was scored 8.1 out of 10 under the CVSS 3.1 framework, putting it in the high-severity category. Singapore’s Cyber Security Agency (CSA) flagged it on November 17, 2026, saying active exploitation is underway. A proof of concept (PoC) is publicly available, although details about the number of compromised systems remain unclear. Earlier, on November 11, Apache released version 2.4.71 to address this vulnerability. When the patch dropped, researchers at Wiz found no signs of active exploitation—but that status has since shifted.

According to vendor advisories, all Apache HTTP Server releases from 2.4.55 through 2.4.70 with mod_http2 enabled are vulnerable. Standalone mod_h2 versions 2.0.8 through 2.0.42 are also at risk. Wiz further noted that among cloud environments examined, 64% run affected Apache builds—and 51% of those are publicly exposed, though not all have HTTP/2 turned on. This represents a large attack surface for potential exploits.

What administrators must do

To secure systems, update Apache HTTP Server to version 2.4.71 or higher, or apply OS-vendor packages that include the patch. If deploying the patch immediately isn’t feasible, disable HTTP/2 by setting “Protocols http/1.1” and verify that virtual hosts don’t accept h2 or h2c. After making changes, reload the service, then check listeners to confirm HTTP/2 is blocked where it should be. Prioritize public-facing servers, but internal systems should be reviewed too. It’s also important to retain and analyze logs to detect possible exploitation before patching took place.

This vulnerability comes on top of a previous Apache HTTP/2 RCE fix released in May, which does not cover CVE-2026-119618. Responsible reporting authors credited both Anthropic’s OSS Scanner and Google Cloud researchers Anthony Weems and Simon Scannell for independently discovering the flaw in late October / early November. Detailed security advisories list all affected versions and configuration considerations.

Why this matters:Remote code execution vulnerabilities are among the most dangerous flaws in web infrastructure. Apache HTTP Server remains foundational for serving millions of sites globally. A flaw this severe—and one that’s actively exploited—raises the risk not just of site defacement, but full system takeover. Watch closely for signs of compromise, particularly in publicly exposed or cloud-hosted Apache installs. Applying the patch isn’t optional; it’s essential to stay ahead of attackers working fast.