A critical remote code execution (RCE) vulnerability, CVE-2026-119618, has been identified in Apache HTTP Server’s HTTP/2 module (mod_http2), affecting versions from 2.4.55 to 2.4.70. The flaw, stemming from a race condition in the assign_headers() function, allows unauthenticated attackers to trigger heap corruption and execute arbitrary code. With 64% of cloud environments reportedly running vulnerable instances, and over half publicly exposed, the risk of lateral movement and cloud infrastructure compromise is substantial.
Although there are no confirmed reports of in-the-wild exploitation, Red Hat has rated the vulnerability CVSS 3.1 9.8 (Critical), noting that public research has demonstrated a reliable exploit on default-configured servers. Apache officially rated the flaw ‘critical’ and released version 2.4.71 on 11 November 2026 to address it. Wiz Research reports that 51% of vulnerable cloud environments have publicly accessible instances, amplifying the urgency.
What the vulnerability entails
CVE-2026-119618 is a concurrency flaw classified under CWE-362 (Concurrent Execution Using Shared Resource with Improper Synchronization). It occurs when multiple HTTP/2 requests are processed simultaneously, leading to unsynchronised access to shared memory in the assign_headers() function. This race condition enables heap memory corruption, which can be weaponised to achieve RCE. The attacker needs no authentication and only requires network access to the server. Notably, only servers with HTTP/2 enabled are at risk; those running HTTP/1.1 exclusively are unaffected.
The vulnerability was independently discovered by Anthropic’s OSS Scanner (as ANT-2026-MAPKT6MZ) and researchers from Google Cloud’s Vulnerability Research team. Apache credited both in its advisory, with initial reports submitted on 26 October and 3 November 2026, followed by a coordinated fix released on 11 November.
Affected systems and patching status
The vulnerability impacts Apache HTTP Server versions 2.4.55 through 2.4.70. The official fix is version 2.4.71 or later. Standalone mod_h2 builds from GitHub (versions 2.0.8 to 2.0.42) are also affected, though no updated release has been published as of 13 November 2026.
Major Linux distributions have rolled out patched packages: Debian (sid, bookworm, trixie), Ubuntu (22.04 LTS and later), and Red Hat Enterprise Linux 9 and 10. Red Hat notes that its mod_http2 implementation includes mitigating factors—separate stream allocators—that reduce exploit reliability, hence its lower severity rating (Important) for RHEL, despite the underlying flaw being Critical. JBoss Core Services and Red Hat Hardened Images remain without fixed packages as of the latest update.
Mitigation and operational guidance
Organisations should prioritise upgrading to Apache HTTP Server 2.4.71 or their distribution’s patched equivalent. For those unable to patch immediately, Red Hat and Wiz recommend disabling HTTP/2 by modifying the Protocols directive in the configuration file to Protocols http/1.1, followed by a server restart. This removes the attack surface temporarily but is not a long-term substitute for patching.
Security teams should audit all Apache deployments, especially internet-facing ones. Wiz offers a pre-built query in its Threat Center to detect vulnerable instances. Organisations relying on third-party vendors should formally inquire whether their services run patched versions, the timeline for remediation, and whether HTTP/2 has been disabled in interim.
What it means
For businesses in the UK, UAE, US, and Kazakhstan, this vulnerability represents a systemic risk to web infrastructure. Apache remains one of the most widely used web servers globally, particularly in cloud-hosted and containerised environments. A successful exploit could lead to full server compromise, data exfiltration, or use as a pivot point for internal network attacks.
The high exposure rate—64% of cloud environments—underscores the challenge of maintaining timely patch cycles, especially in distributed systems. The availability of a demonstrated exploit, even without active abuse, increases the likelihood of weaponisation by opportunistic threat actors.
Immediate actions for IT leaders
Prioritise inventorying all Apache HTTP Server instances, confirm patch status, and apply updates immediately. For critical systems with patching delays, disable HTTP/2. Verify vendor compliance through formal inquiry. Monitor logs for unusual HTTP/2 traffic patterns, though no official IoCs have been released. Given the severity, treat this as a top-tier vulnerability until full remediation is confirmed.