Cybersecurity Research

Critical Apache Web Server Flaw Could Let Attackers Take Over Servers Remotely

Wiz Research · 12 Nov 2026
Key Takeaway Check whether your web servers run Apache with HTTP/2 enabled, then update to version 2.4.71 or later, or switch HTTP/2 off until you can patch.

Wiz Research has detailed a critical vulnerability, CVE-2026-119618, in the HTTP/2 module (mod_http2) of Apache HTTP Server. The flaw is a race condition in the assign_headers() function, where concurrent threads share resources without proper synchronisation. A remote attacker with no login could use it to corrupt memory and run commands on the server with the privileges of the web server process. It was independently discovered by Anthropic and Google Cloud's Vulnerability Research Team.

At the time of publication, no exploit was available and there were no reports of exploitation in the wild. However, Wiz data suggests the exposure is wide: 64% of cloud environments have resources vulnerable to the flaw, and 51% have publicly exposed instances. Wiz notes these figures do not take configuration into account. In cloud setups, a compromised Apache server could also be a stepping stone to nearby services or cloud metadata endpoints.

The fix is to upgrade Apache HTTP Server to version 2.4.71 or later. Anyone running standalone mod_h2 builds from GitHub should move to a version newer than 2.0.42. If patching cannot happen straight away, HTTP/2 can be temporarily disabled by limiting the server to HTTP/1.1 in its configuration file and removing the h2 and h2c references. This article is based on the opening section of the Wiz Research post, so check the full advisory for the complete list of affected versions.

Summarised by CISO AI from Wiz Research, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.