Summary
- Apache HTTP Server versions 2.4.55 through 2.4.70 are affected by CVE-2026-119618 when the vulnerable HTTP/2 implementation is enabled.
- Apache released version 2.4.71 on 11 November, and NHS England published a subsequent security alert after proof-of-concept material became available.
- Successful exploitation could permit remote code execution, although public reporting has not established confirmed attacks against production systems.
A critical vulnerability in Apache HTTP Server could allow unauthenticated attackers to execute code on affected systems, prompting warnings to organisations operating web infrastructure with the HTTP/2 protocol enabled.
The Apache Software Foundation released version 2.4.71 on 11 November to address the flaw, identified as CVE-2026-119618. The vulnerability affects Apache HTTP Server versions 2.4.55 through 2.4.70 where the vulnerable HTTP/2 component is active.
NHS England issued a cybersecurity alert the following day after proof-of-concept material became publicly available. Its National Cyber Security Operations Centre assessed exploitation as likely, although that assessment does not establish that attackers have successfully compromised production systems using the flaw.
The vulnerability involves improper synchronisation between concurrent operations within Apache’s mod_http2 module. Under certain conditions, the resulting race condition can corrupt server memory and potentially allow remote code execution without valid user credentials.
Concurrent processing creates the vulnerability
HTTP/2 allows multiple requests and responses to share a network connection, improving efficiency compared with earlier approaches to transferring web content. Apache uses the mod_http2 module to implement the protocol alongside the server’s wider request-processing functions.
The vulnerability concerns how the module manages shared information when concurrent operations assign response headers. If those operations interact without sufficient synchronisation, the software can reach an inconsistent memory state.
Such race conditions arise when the result of a process depends on the timing of activities accessing shared resources. Where the affected code is reachable through external requests, an attacker may be able to trigger behaviour that compromises the memory of the server process.
Apache classifies the issue as critical because successful exploitation could lead to arbitrary code execution. That consequence is more serious than a simple application crash, as it can potentially allow malicious actions to be performed using the privileges available to the affected server process.
However, the presence of a vulnerable software version does not automatically mean every Apache deployment can be attacked through this issue. The HTTP/2 component must be enabled and reachable under an affected configuration.
Servers operating exclusively with HTTP/1.1 are not exposed to CVE-2026-119618 through mod_http2. Administrators therefore need to establish both the installed software and the protocols actually in use.
The advisory also covers versions 2.0.8 through 2.0.42 of the separate icing/mod_h2 project. That repository was archived in June 2026 and no longer receives security maintenance, leaving users dependent on migration to a supported implementation rather than expecting a new standalone patch.
Public research increases remediation urgency
Apache received reports of the issue from Anthropic’s OSS Scanner in late October and researchers at Google Cloud Vulnerability Research in early November. The project released its corrected version on 11 November.
Security researchers subsequently published proof-of-concept material examining the flaw. Public technical analysis has demonstrated memory corruption in an affected version, while the availability of a reliable exploit capable of achieving code execution in arbitrary real-world environments has not been independently established.
These distinctions are important when assessing the available evidence. A critical vulnerability rating identifies the potential technical consequence, while proof-of-concept material demonstrates aspects of exploitability. Confirmed malicious exploitation is a separate finding requiring evidence that an attacker has used the weakness against an actual target.
NHS England’s warning reflects the increased risk created by public disclosure and the possible consequences for affected systems. Its assessment that exploitation is likely does not amount to confirmation that a widespread campaign is already under way.
By 13 November, publicly available security assessments had not established confirmed exploitation in production environments. That absence of confirmation does not reduce the importance of applying the available fix, particularly where affected services are exposed to external traffic.
Organisations may also need to monitor whether new evidence emerges after initial disclosure. Security advisories often change as researchers examine the vulnerability, software maintainers distribute updates, and defenders investigate attempted exploitation.
Checking exposure requires configuration knowledge
Administrators should identify affected installations and establish whether HTTP/2 is enabled. The public version information returned by a web server may not provide sufficient evidence of its underlying configuration or the patches installed through a distribution’s maintenance system.
Some Linux distributions and commercial providers apply security fixes to maintained packages without immediately adopting the latest upstream version number. An organisation may therefore need to consult its operating system vendor’s advisory rather than rely exclusively on the version string displayed by the server.
Infrastructure architecture introduces further complications. Public requests may pass through a content delivery network, load balancer, or reverse proxy before reaching Apache, and the protocol used on each connection can differ.
A server behind a proxy may still process HTTP/2 connections if that protocol is enabled between the intermediary and the application infrastructure. Conversely, an external HTTP/2 connection does not establish that the Apache component behind the intermediary is itself exposed.
Understanding those arrangements is necessary before determining which systems require immediate remediation and whether temporary restrictions would reduce the relevant exposure.
The recommended permanent response is to install Apache HTTP Server 2.4.71 or a later fixed release, or the appropriate patched package supplied by a supported distribution.
Where updating cannot be completed immediately, NHS England advises temporarily disabling HTTP/2 and restricting the active protocols to HTTP/1.1, subject to compatibility and performance requirements.
Such a restriction may affect applications or infrastructure configured to rely on HTTP/2 functionality. It should therefore be assessed and tested, with the permanent software fix applied as soon as practical.
Maintenance responsibility can span several providers
Apache HTTP Server is deployed in a wide variety of hosting environments, from internally managed applications to services operated through external infrastructure providers.
Responsibility for applying a security update can depend on those arrangements. A managed hosting customer may rely on its provider to patch the server, while an organisation operating its own infrastructure must coordinate software updates with application testing and maintenance windows.
Systems embedded within appliances or bundled software packages can introduce additional dependencies. An organisation may know that Apache is present without having direct authority to update the component independently of the supplier responsible for the wider product.
Asset inventories need to identify the affected service, its configuration, operational owner, and remediation route. A critical advisory can be difficult to act upon where those details are incomplete or distributed between several teams.
The 2.4.71 release also addresses two other vulnerabilities: CVE-2026-106023, involving a possible crash in mod_md, and CVE-2026-109163, a lower-severity memory issue in mod_vhost_alias. Administrators reviewing the update should account for the complete security release.
For CVE-2026-119618, the immediate requirement is to determine which HTTP/2-enabled deployments remain affected and apply the relevant fix. With a corrected version available and public research increasing knowledge of the weakness, the window for leaving vulnerable web infrastructure unpatched is narrowing.












