CVE-2026-119618: Unauthenticated RCE in Apache HTTP Server mod_http2 assign_headers()
- Vendor
- Icing
CVE-2026-119618 is a race condition in the assign_headers() function of Apache HTTP Server's mod_http2 module. Improper synchronization between connection and stream worker threads allows concurrent access to shared header-processing memory, potentially causing heap corruption. An unauthenticated remote attacker can trigger the vulnerability through specially crafted concurrent HTTP/2 requests and potentially execute arbitrary code with the web-server worker process's privileges. Affected versions are Apache HTTP Server 2.4.55 through 2.4.70 and separately distributed mod_h2 2.0.8 through 2.0.42. Exploitation requires mod_http2 to be loaded and HTTP/2 to be enabled; HTTP/1.1-only deployments are not affected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise the confidentiality, integrity, and availability of resources accessible to the Apache worker process. Consequences include unauthorized access to application data and credentials, modification of accessible files, and execution of attacker-controlled commands. Heap corruption can also crash worker processes and disrupt service. Further compromise of backend systems or lateral movement depends on the server's permissions, credentials, and network access; elevated operating-system privileges are not inherently granted.
Mitigation
If you can’t patch tonight, do this now.
Until patching is possible, disable HTTP/2 by removing h2 and h2c from every applicable server-wide and virtual-host Protocols directive, leaving Protocols http/1.1, or unload mod_http2. Restart Apache to apply the configuration and verify that HTTP/2 is no longer available. Check dependencies such as gRPC backends before disabling HTTP/2. Monitor for unexpected worker crashes, child-process execution, and outbound connections while remediation proceeds.
Remediation
Patch, then assume compromise.
Upgrade Apache HTTP Server to version 2.4.71 or later, or install a distribution or product-vendor security update that backports the fix. Restart affected Apache processes after updating. Rebuild and redeploy container images containing vulnerable components rather than merely restarting existing containers. Standalone mod_h2 users can migrate to the fixed module bundled with Apache HTTP Server; the availability of a standalone 2.0.43 fix is inconsistently documented.
Exploits
4 exploits validated by Mallory's analysis. Hidden: 11 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-119618 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-119618 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-119618?
- Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2026-119618, the earliest disclosed Nov 12, 2026.
- Is there a patch for CVE-2026-119618?
- Upgrade Apache HTTP Server to version 2.4.71 or later, or install a distribution or product-vendor security update that backports the fix. Restart affected Apache processes after updating.
- What products are affected by CVE-2026-119618?
- Icing Mod Http2.
- How severe is CVE-2026-119618?
- CVE-2026-119618 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 1.6% (76th percentile) as of Nov 17, 2026.
Recent activity
334 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.