
A critical security vulnerability in Apache HTTP Server could allow remote attackers to execute arbitrary code on vulnerable servers through HTTP/2 connections. The flaw, tracked as CVE-2026-119618, affects Apache’s mod_http2 module and is caused by a race condition that can lead to heap memory corruption.
The vulnerability affects Apache HTTP Server versions 2.4.55 through 2.4.70 when HTTP/2 is enabled, as well as certain standalone mod_h2 versions and Linux distribution packages. Apache addressed the issue with the release of version 2.4.71 on November 11, 2026.
Security teams are urged to prioritize patching internet-facing web servers and temporarily disable HTTP/2 on vulnerable systems where immediate updates are not possible.
Vulnerability details
CVE-2026-119618 stems from a race condition in the assign_headers() function of Apache’s HTTP/2 module. The flaw occurs when concurrent request-processing threads interact with shared memory in an unsafe manner, potentially resulting in heap corruption.
Under specific conditions, an attacker can trigger the vulnerability by sending crafted HTTP/2 requests to a vulnerable server. Successful exploitation could allow arbitrary code execution within the privileges of the Apache web server process.
The vulnerability is particularly concerning because it does not require authentication or user interaction. Attackers may exploit exposed servers remotely if HTTP/2 is enabled and the vulnerable code is present.
Depending on the privileges of the web server process, successful exploitation could allow attackers to access application files, configuration data, credentials, session information, and other sensitive resources available to the service account.
Affected systems
The vulnerability affects the following software:
- Apache HTTP Server versions 2.4.55 through 2.4.70 with HTTP/2 enabled.
- Standalone
mod_h2versions 2.0.8 through 2.0.42. - Certain Ubuntu Apache packages, including installations running versions 2.4.41 and 2.4.52, due to affected module implementations and distribution packaging.
Systems running Apache without HTTP/2 enabled are not exposed to this specific vulnerability.
Administrators should note that distribution-maintained packages may include security fixes through backports, meaning the upstream Apache version number alone may not accurately determine whether a system is vulnerable.
Severity and exploitation status
The vulnerability has received differing severity assessments from security organizations. Red Hat assigns a CVSS score of 9.8, classifying it as Critical, while CISA’s assessment is 8.1.
Although Apache and CISA have not reported confirmed exploitation in the wild at the time of the referenced advisory, public research has reportedly demonstrated reliable exploitation, and repositories claiming proof-of-concept exploit code have appeared online.
The availability of public technical research increases the risk of exploitation attempts, particularly against internet-facing Apache deployments that have not yet been patched.
Security updates released
Apache addressed CVE-2026-119618 in version 2.4.71, released on November 11, 2026.
Linux distributions have also published security updates for affected packages, including:
- Debian: Security updates for Debian 12 and 13.
- Ubuntu: Updates released through USN-9090-1, covering affected supported releases.
- Red Hat Enterprise Linux: Security updates for the
mod_http2package on RHEL 9 and 10. - SUSE: Security updates released on November 14, 2026.
Administrators running Apache from source or upstream binaries should upgrade to version 2.4.71. Users relying on distribution packages should install the security updates provided by their respective vendors.
Recommended mitigation measures
Organizations are advised to take the following actions as soon as possible:
- Identify all Apache HTTP Server instances across their infrastructure.
- Determine whether the
mod_http2module is loaded and HTTP/2 is enabled. - Upgrade vulnerable installations to Apache 2.4.71 or the appropriate vendor-patched package.
- Restart Apache services after applying updates to ensure the patched modules are loaded.
- Temporarily disable HTTP/2 on systems that cannot be patched immediately.
- Prioritize internet-facing servers, reverse proxies, containerized workloads, and Apache installations bundled with third-party applications or control panels.
Disabling HTTP/2 can reduce exposure while patching is underway. Administrators can configure Apache to use HTTP/1.1 only by setting Protocols http/1.1 and restarting the service, ensuring the configuration is applied to all relevant virtual hosts.
Detection and threat hunting
Security teams should investigate unusual Apache process crashes, segmentation faults, memory corruption errors, and abnormal request bursts involving HTTP/2.
Potential post-exploitation indicators include:
- Apache child processes launching shells, scripting interpreters, or download utilities.
- Unexpected files or executable payloads created in web directories or temporary locations.
- Unusual outbound network connections originating from Apache processes.
- Unauthorized modifications to scheduled tasks, SSH keys, startup scripts, or other persistence mechanisms.
- Abnormal HTTP/2 request patterns preceding Apache process crashes.
A server exhibiting suspicious activity should be isolated for investigation. Logs and forensic evidence should be preserved, and confirmed compromised systems should be rebuilt from trusted sources after remediation.
Organizations should also rotate application credentials, database passwords, API keys, session secrets, and other sensitive information accessible to the compromised web server process.
Conclusion
CVE-2026-119618 represents a serious security risk for organizations operating Apache HTTP Server with HTTP/2 enabled. The combination of remote exploitability, potential code execution, and publicly available technical research makes timely remediation a priority.
While confirmed exploitation has not been reported in the referenced advisory, organizations should not wait for attacks to emerge before taking action. Identifying vulnerable deployments, applying vendor updates, temporarily disabling HTTP/2 where necessary, and monitoring for suspicious activity are essential steps to reduce the risk of compromise.
Security advisory: ThreatDefence – Apache CVE-2026-119618 HTTP/2 RCE: Patching and Hunting
