Apache HTTP Server CVE-2026-119618 Patched After Critical HTTP/2 Flaw
Apache patched a critical remote code execution vulnerability, CVE-2026-119618, in its HTTP Server versions 2.4.55 through 2.4.70. The flaw in the HTTP/2 module allows unauthenticated attackers to execute arbitrary code, with cloud security firm Wiz reporting vulnerable versions in 64% of cloud environments.

A critical remote code execution flaw in Apache HTTP Server's HTTP/2 module affects cloud environments. The vulnerability, tracked as CVE-2026-119618, is a race condition in the mod_http2 module that corrupts heap memory, allowing an unauthenticated remote attacker to achieve arbitrary code execution with web server privileges. Apache describes the issue as a 'Concurrent Execution using Shared Resource with Improper Synchronization vulnerability'. The flaw was patched on November 11 with the release of Apache HTTP Server version 2.4.71.
CVE-2026-119618 affects Apache HTTP Server versions 2.4.55 through 2.4.70 and standalone mod_h2 builds 2.0.8 through 2.0.42. The vulnerability was discovered independently by Anthropic’s OSS Scanner, which reported it on October 26, and by Google Cloud’s Vulnerability Research team eight days later. Red Hat assigned the flaw a CVSS score of 9.8 out of 10, rating it critical. Red Hat said: "only servers that have HTTP/2 enabled are affected; servers configured to serve only HTTP/1.1 are not vulnerable."
Scope of impact in cloud environments
Cloud security company Wiz indicates that 64% of cloud environments contain resources running the affected Apache versions. Roughly half of these vulnerable instances are publicly exposed, irrespective of their HTTP/2 configuration. This widespread presence shows the urgency for cloud security teams to scan their infrastructure. HTTP/2 must be explicitly enabled for the vulnerability to be exploitable, as it is disabled by default in Apache configurations.
Patch availability and remediation
Remediation requires upgrading Apache HTTP Server to version 2.4.71 or later. Standalone mod_h2 builds must be upgraded to a version newer than 2.0.42. As a temporary mitigation, disabling HTTP/2 by removing h2 and h2c from the protocol list in the httpd.conf configuration file eliminates the attack vector. The latest Apache release also addresses two other vulnerabilities.
| CVE Identifier | Severity | Affected Module | Issue Type |
|---|---|---|---|
| CVE-2026-119618 | Critical | mod_http2 | Race condition leading to RCE |
| CVE-2026-106023 | Important | mod_md | Null pointer dereference |
| CVE-2026-109163 | Low | mod_vhost_alias | Data overwrite |
Discovery and current threat status
The flaw was found through separate research efforts. No public exploit demonstrating full remote code execution is known, and no exploitation in the wild has been reported as of the patch release date. A public proof-of-concept demonstrates memory corruption and Apache process crashes but does not show code execution. Wiz provides a pre-built query in its Threat Center for locating vulnerable instances. Defiant, a WordPress security firm, warned that WordPress updates cannot resolve this underlying server vulnerability.
Vendor responses and distribution updates
Vendor responses have varied. Red Hat has shipped fixes for its Enterprise Linux distributions, rating the flaw as Important. Debian has fixed the issue in its unstable branch, while other versions remain vulnerable. Amazon Linux lists the fix as pending. The standalone mod_h2 project presents a challenge, as its GitHub repository has been read-only since June, leaving users with no fixed release to install. The path forward is clear. Upgrading to Apache HTTP Server version 2.4.71 or later is the definitive solution.





