Apache Fixes Critical HTTP/2 Race Condition Enabling Unauthenticated RCE

Summary
Apache fixed CVE-2026-119618, a critical mod_http2 race condition affecting versions 2.4.55–2.4.70 when HTTP/2 is enabled. Upgrade to 2.4.71 or vendor-fixed packages; no in-the-wild exploitation was reported as of Nov. 12, 2026.
Key points
- Improper synchronization during concurrent HTTP/2 processing can corrupt heap memory and potentially enable unauthenticated remote code execution as the Apache process.
- Apache HTTP Server versions 2.4.55–2.4.70 are affected when mod_http2 and HTTP/2 are enabled; standalone mod_h2 versions 2.0.8–2.0.42 are also affected.
- HTTP/1.1-only configurations do not reach the vulnerable code path. Administrators should check global and virtual-host settings for h2 or h2c.
- Apache released the fix in HTTP Server 2.4.71 on Nov. 11, 2026. Red Hat also released corrected packages for RHEL 9 and 10; use distribution advisories to account for backported fixes.
- Red Hat reports reliable exploitation demonstrated in research, but the article says no reviewed sources reported real-world exploitation as of Nov. 12, 2026.
- If patching is delayed, temporarily disabling HTTP/2 can reduce exposure; the article recommends upgrading as the primary remediation.
Article Details
- Vulnerability Types
- Race condition
- Heap corruption
- Remote code execution
- Severity
- Critical; Red Hat assigns CVSS 3.1 9.8 generally and Important on RHEL 9 and RHEL 10.
- Affected Versions
- Apache HTTP Server 2.4.55 through 2.4.70
- Standalone mod_h2 2.0.8 through 2.0.42
- Exploitation Status
- not_reported
- Exploit Availability
- none_reported
- Patch Status
- available
- Workarounds
- Temporarily disable HTTP/2 by configuring Protocols http/1.1 and checking global and virtual-host configurations for h2 or h2c.
MITRE ATT&CK
CVE
People
Vendors
ApacheApache has released an urgent security update addressing CVE-2026-119618, a critical remote code execution vulnerability in the mod_http2 module of Apache HTTP Server.Red HatRed Hat has assigned the vulnerability a CVSS 3.1 score of 9.8 for its general assessment, with network-accessible, low-complexity exploitation requiring neither authentication nor user interaction.
