← cd ../blog

CVE-2026-119618: Apache HTTP/2 race condition leading to RCE

A race condition in mod_http2 (CVSS 9.8) corrupts heap memory and can lead to remote code execution. Who's exposed, how to check, and the fix in 2.4.71.

The second of three critical RCE flaws this week. This one needs HTTP/2 enabled, and there’s no confirmed in-the-wild exploitation yet — but it’s unauthenticated and rated 9.8, so it belongs on the short list. See also the actively-exploited Apache Roller RCE, the Linux kernel TCP flaw, and the 2026 RCE field guide.

Scope and ethics. Exposure detection and remediation only, for systems you own or are authorized to test. No weaponized exploit here.

Description

A race condition (CWE-362) in the assign_headers() function of mod_http2. Concurrent worker threads access a shared header table without proper synchronization, which corrupts heap memory. Crafted concurrent HTTP/2 requests can turn that corruption into remote code execution in the web-server process.

Impact

Heap corruption in httpd worker processes, leading to potential RCE and denial of service. The blast radius is every internet-facing Apache front end and reverse proxy that speaks HTTP/2 — often the most exposed box in the estate.

Prerequisites (for the attack to work)

  • HTTP/2 enabled via the Protocols directive (h2 over TLS or h2c cleartext). HTTP/1.1-only servers are not affected.
  • A vulnerable build: Apache httpd 2.4.55 – 2.4.70, or standalone mod_h2 2.0.8 – 2.0.42. RHEL 9/10 and third-party products that bundle Apache with HTTP/2 are also in scope.
  • No authentication, no user interaction.

Steps to reproduce (exposure validation)

# 1) Version of the running server
httpd -v 2>/dev/null || apachectl -v

# 2) Is mod_http2 actually loaded?
apachectl -M 2>/dev/null | grep -i http2

# 3) Any vhost negotiating h2/h2c anywhere in the config tree?
grep -RniE "Protocols .*h2c?\b" /etc/httpd /etc/apache2 2>/dev/null

# 4) From the outside: does the host negotiate HTTP/2?
curl -sI --http2 https://www.example.com | head -n1   # "HTTP/2 200" = negotiated

Module loaded + a Protocols line with h2/h2c + version ≤ 2.4.70 = exposed. To study the memory corruption itself, reproduce it against your own 2.4.70 build in a lab using the public research linked below.

Remediation

  1. Upgrade to Apache HTTP Server 2.4.71 (released 2026-11-11). The same release also fixes CVE-2026-106023 (mod_md) and CVE-2026-109163 (mod_vhost_alias).
  2. Interim mitigations — they reduce exposure but are not a substitute for the patch:
    • Restrict Protocols to http/1.1.
    • Stop loading mod_http2 if you don’t actually need HTTP/2.
    • Terminate HTTP/2 at an unaffected load balancer or CDN in front of the origin.
    • Apply least privilege: restrict outbound access from web servers and don’t mount unnecessary credentials into web containers.
  3. Monitoring: Apache published no IOCs. Treat httpd child segfaults in the error log, anomalous HTTP/2 traffic patterns, and unexpected processes under the web-server account as possible exploitation signals.

References

Verify every version against the vendor advisory before acting. Published 18 Nov 2026.