The Apache Software Foundation has released fixes for a critical vulnerability in the HTTP/2 module of Apache HTTP Server that could allow an unauthenticated attacker to achieve remote code execution. The flaw is tracked as CVE-2026-119618, and researchers warn that a significant number of internet-facing servers are exposed.

What the flaw is

The vulnerability is a race condition in the mod_http2 module. Improper synchronization when concurrent threads access a shared resource allows an attacker to trigger heap corruption. Apache’s advisory describes the issue as concurrent execution using a shared resource with improper synchronization in the assign_headers() function. The bug was discovered by Anthropic’s OSS Scanner and Google Cloud’s Vulnerability Research teams.

Affected versions

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

A successful exploit would let an attacker run arbitrary commands with the privileges of the web server process.

Exposure and configuration

Apache HTTP Server is widely deployed and is estimated to power roughly one in five websites. Telemetry from cloud security firm Wiz indicates that 64% of cloud environments contain vulnerable resources, and about half of those have publicly exposed instances. These figures do not account for configuration, however. HTTP/2 must be enabled for a server to be affected, and it is disabled by default. Researchers at watchTowr confirmed this condition and recommended that administrators either patch immediately or disable h2 until they can.

Severity and exploitation status

Wiz assesses the vulnerability as critical, although no official CVSS score has been published. As of the reporting, Wiz is not aware of any public exploits or active attacks targeting the flaw, but it notes that this could change quickly.

Other fixes in the release

The same update also addresses two additional issues: CVE-2026-106023, a null pointer dereference in mod_md, and CVE-2026-109163, a low-severity data overwrite flaw in mod_vhost_alias.

Recommended actions

  • Upgrade Apache HTTP Server to a fixed release as soon as possible.
  • Check whether HTTP/2 is enabled on your servers, since unaffected configurations do not require the same urgency.
  • If patching cannot happen immediately, consider disabling HTTP/2 as a temporary mitigation.
  • Prioritize internet-facing instances and cloud workloads for review.