Security advisory · Apache HTTP Server
Heap corruption in Apache httpd mod_http2 can lead to remote code execution
CVE-2026-119618 is a memory-corruption flaw in the Apache HTTP Server’s mod_http2 module that can lead to remote code execution. Only servers that load mod_http2 and enable HTTP/2 are affected. Issuers rate it differently, from high to critical, so every number here carries its source. The fix is to update to Apache HTTP Server 2.4.71.
What is affected and the precondition
The flaw is a race condition in the mod_http2 module’s assign_headers() function that can
corrupt the heap and lead to remote code execution. Apache and the CVE record classify it as
CWE-362 (improper synchronization); Red Hat classifies it as CWE-20, an example of issuers
describing the same flaw differently.
It is reachable over the network without authentication, but only under one condition: the
server must load mod_http2 and have HTTP/2 enabled, through h2 or h2c in the
Protocols directive. A server that speaks only HTTP/1.1 is not affected, and HTTP/1.1 is
the upstream default, so HTTP/2 has to be turned on deliberately.
Severity, quoted with its issuer
Different organizations scored this flaw differently. We quote each rating with the organization that issued it, and we do not pick one as “the” number.
| Issuer | Rating |
|---|---|
| Apache (CNA) | Labelled “critical” (the project’s own label, no CVSS score) |
| CISA ADP (Vulnrichment) | CVSS 3.1 8.1 (high) |
| Red Hat | Critical; CVSS 3.1 9.8 (rated Important for RHEL 9 and 10) |
| CSA Singapore | High-severity, citing CVSS 3.1 8.1 |
| Ubuntu | Priority high |
What is known about exploitation
Singapore’s Cyber Security Agency (CSA), in alert AL-2026-164 of 17 November 2026, says the flaw is “reportedly being actively exploited, and a proof-of-concept exploit is publicly available”, without naming the source of the exploitation. CISA’s own SSVC assessment of 13 November 2026 recorded exploitation status as none, and as of the 18 November 2026 catalog the CVE is not in the CISA Known Exploited Vulnerabilities list. A public proof of concept reproduces the heap corruption; whether a public exploit achieves code execution is unconfirmed, with Red Hat stating a reliable exploit exists but not linking it, and Horizon3 reporting that the available proof of concept does not demonstrate code execution. We treat active exploitation as reported by CSA Singapore, not confirmed.
How to check your exposure from outside
Run these checks only on servers you own or are authorized to test. They read the server’s banner and its TLS handshake; they send no payloads.
-
Read the Server header
Look for a
Server: Apache/2.4.xheader where x is between 55 and 70 inclusive, the affected range 2.4.55 through 2.4.70. -
Check whether HTTP/2 is negotiated
In a normal TLS handshake, see whether the server selects
h2through ALPN. If it does not offer HTTP/2, the precondition is not met. This is the handshake only. -
Mind what hides the signal
ServerTokens Prodhides the version; cleartexth2cis not visible through ALPN; and a CDN or proxy in front answers the handshake on behalf of the origin. -
Remember backports
A distribution build can be patched without a version change, or even affected below 2.4.55 because a newer module was backported. The version is a signal, not a proof.
How to fix it
- Update to Apache HTTP Server 2.4.71. Apache publishes no workaround; updating is the remediation.
- If you cannot update right away, Red Hat’s mitigation is to remove
h2andh2cfrom everyProtocolsdirective, leavingProtocols http/1.1, and restart the server. Confirm afterwards that requests fall back to HTTP/1.1. - For distribution packages, apply the distribution’s advisory rather than comparing the upstream version number, which backports can make misleading.
How NorthBound looks at this
As part of tech stack intelligence, we recognize web-server software and match it to new CVEs with CISA KEV and exploitation context. For this flaw the external signal is the server version together with HTTP/2 negotiated by ALPN, so we keep it tentative: a production banner, cleartext HTTP/2, a proxy in front, or a backported package can all break the version signal. Our team reviews each match, and the check is a handshake, never a payload against the vulnerable code.
Sources
- Apache HTTP Server security advisory (fixed in 2.4.71).
- CVE-2026-119618 record and the NVD entry.
- CSA Singapore alert AL-2026-164.
Find it before an attacker does.
Tell us what you need covered. We will reply from contact@northboundintelligence.com to arrange a scoping call.
Facts on this page verified 11 November 2026.