CVE-2026-119618: Apache HTTP/2 RCE
Apache’s HTTP/2 flaw can allow remote code execution. Check affected versions, distribution fixes and how to disable HTTP/2 while you patch.
Reviewed by Codex · 13 November 2026

CVE-2026-119618 is a critical vulnerability in Apache HTTP Server’s mod_http2 module. Apache released the fix in 2.4.71 on 11 November 2026. For teams operating Apache, the immediate task is to identify affected builds, establish whether HTTP/2 reaches them and deploy the appropriate update. Apache’s advisory confirms the affected versions and release.
Which installations need attention?
- Apache HTTP Server 2.4.55–2.4.70 is the affected upstream range. The fixed release is 2.4.71. Apache advisory.
- Standalone mod_h2 2.0.8–2.0.42 is also affected, according to the original announcement. If you install the module separately, check its own build and patch status.
- HTTP/2 must be enabled. Red Hat says HTTP/1.1-only servers are not affected by this flaw. It also reports a reliable public exploit against a default-configured server with mod_http2 enabled. Red Hat assessment.
Amazon Linux assigns a CVSS 3.1 score of 9.8, with no authentication or user interaction required. Its tracker now lists fixes for Amazon Linux 2 and 2023, released on 12 November. Check the linked advisory for the exact package release applicable to your system. Amazon Linux tracker.
A small change at a memory boundary
Apache describes a synchronization flaw in assign_headers() that can lead to remote code execution. The upstream patch changes which header table receives a synthesized Content-Length value: the write moves from req->headers to r->headers_in. The security lesson is about ownership: a small-looking write can matter greatly when concurrent work shares memory. The patch’s size says little about the potential impact.
A published exploit demonstrates a capability; it does not establish that a particular installation has been compromised. This article is a review of public sources. Bracemont has not reproduced exploitation or assessed any deployed server for this article.
Check the package, not just the banner
Distribution builds can differ. Red Hat rates its RHEL 9 and 10 packages Important, citing allocator differences that make exploitation harder; it lists RHEL 8 and earlier as unaffected. Those statements concern Red Hat’s packages, not every custom installation on those operating systems. Product-specific assessment.
Vendors also backport security fixes into older releases. An older upstream version string can therefore belong to a patched package. Record the complete package version and its supplier’s advisory. Conversely, do not dismiss an alert merely because the distribution commonly backports fixes: confirm that this CVE is covered by the package actually installed.
If patching must wait, disable HTTP/2 completely
Apache uses h2 for HTTP/2 over TLS and h2c for cleartext connections. Its HTTP/2 guide shows that support can be configured globally or per virtual host. Where service requirements permit a temporary HTTP/1.1-only configuration, remove both HTTP/2 variants and use Protocols http/1.1.
Check every relevant virtual host: its own Protocols directive replaces the global setting. Changing only the global line can leave HTTP/2 available elsewhere. Validate the configuration, apply it through your normal service-change procedure and verify the effective protocols. Merely putting http/1.1 first in a list that still contains h2 is insufficient.
For a service behind a CDN or reverse proxy, our operational recommendation is to trace each connection separately. What the browser negotiates with the edge does not establish what reaches the origin. Include direct origin access, internal listeners and alternate hostnames in that configuration review.
What to record before closing the ticket
- Inventory: the affected service, owner, installed Apache and module packages, and reachable HTTP/2 listeners.
- Remediation: the vendor advisory, replacement package or image, deployment time and confirmation that running instances use it.
- Verification: the effective configuration and normal service checks after the change. If HTTP/2 was disabled temporarily, assign an owner and date for the permanent update.
For a managed hosting provider, ask for that same evidence. A statement that an update is available leaves the deployment question open. Close the issue when the running service’s state is documented, and keep any investigation of suspected compromise separate from the patching record.