Apache HTTP Server mod_http2 CVE-2026-119618 RCE: update to 2.4.71
Apache HTTP Server 2.4.55 through 2.4.70 has a critical mod_http2 RCE flaw, CVE-2026-119618; update to 2.4.71 or disable HTTP/2.
- Published
- Updated
- Ecosystem
- Websites and CMSOpen sourceCloud
- Fixed in
- Apache HTTP Server 2.4.71; vendor packages such as Red Hat mod_http2-2.0.26-7.el9_9.1 (RHEL 9) and mod_http2-2.0.29-5.el10_3.1 (RHEL 10); Debian unstable apache2 2.4.71-1
- Exploitation
- No confirmed exploitation in the wild; Wiz reported none as of 2026-11-11, while Red Hat says public research demonstrated a reliable exploit (not named)
Live scores
CVE-2026-119618- EPSS
- 0.015
some chance of attack soon - VEDAS
- 0.969
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Live scores
CVE-2026-23918- EPSS
- 0.497
likely to be attacked soon - VEDAS
- 0.981
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Live scores
CVE-2026-106023- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.050
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Live scores
CVE-2026-109163- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.080
little exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
What happened
The Apache HTTP Server project lists CVE-2026-119618 as critical: a concurrent execution flaw with improper synchronization in mod_http2’s assign_headers() that can lead to remote code execution. Apache HTTP Server project says it affects Apache HTTP Server 2.4.55 through 2.4.70, and mod_h2 from GitHub 2.0.8 through 2.0.42. The fix landed in 2.4.x on 2026-11-11, and 2.4.71 was released the same day.
Per the same advisory, Anthropic’s OSS Scanner reported the flaw on 2026-10-26. Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research reported it on 2026-11-03. SecurityWeek describes these as independent discoveries.
SecurityWeek and The Hacker News both cite Red Hat, which rates the flaw 9.8 on CVSS. Red Hat says an unauthenticated remote attacker could execute commands and take control of the server process. It also says only servers with HTTP/2 enabled are affected, and servers serving only HTTP/1.1 are not vulnerable.
On exploitation, the sources differ:
- Wiz said on 2026-11-11 that no exploit was available and no exploitation in the wild had been reported.
- The Hacker News reports that Red Hat’s assessment says public research has demonstrated a reliable exploit against a default-configuration server with mod_http2 enabled. Red Hat does not name or link that research.
- SecurityWeek says a public proof of concept on GitHub reports memory corruption and Apache process crashes but does not demonstrate remote code execution.
Wiz data, as reported by Wiz, says 64% of cloud environments have resources running affected versions and 51% have publicly exposed instances. SecurityWeek notes Wiz cautioned that these figures do not account for configuration, so they do not necessarily show exploitable installs.
Am I affected?
You are likely affected if both of these are true:
- You run Apache HTTP Server 2.4.55 through 2.4.70, or a standalone mod_h2 build from 2.0.8 through 2.0.42 (Apache HTTP Server project).
- HTTP/2 is turned on. Per The Hacker News, HTTP/2 runs only where the Protocols directive enables it, using h2 for HTTP/2 over TLS and h2c for HTTP/2 over plain TCP. It can be set server-wide or per virtual host, so check both.
Version caveat from The Hacker News: servers already updated to 2.4.67 (which fixed an earlier HTTP/2 flaw, CVE-2026-23918) or any later release up to 2.4.70 are still in the affected range.
Distribution status as of 2026-11-12, per The Hacker News:
- Red Hat Enterprise Linux 9 and 10: fixed. Red Hat rates the flaw Important there rather than Critical, because its packages give each HTTP/2 stream its own memory allocator, which makes an attack much harder, per the vendor.
- Red Hat Enterprise Linux 6, 7 and 8: not affected.
- Red Hat JBoss Core Services and Red Hat Hardened Images: affected, no fix listed.
- Debian unstable: fixed in apache2 2.4.71-1. Debian bookworm, trixie and forky: listed as vulnerable, no fix listed.
- Amazon Linux 2, 2023 and 2027 Preview: fix pending.
- Ubuntu: no tracker page when The Hacker News checked.
These statuses change quickly, so check your vendor’s tracker.
The standalone mod_h2 module is a point where sources differ. The Apache advisory gives 2.0.8 through 2.0.42 as affected. Wiz lists “2.0.42 and newer” as patched, while The Hacker News says no fixed mod_h2 release exists, that its GitHub release list ends at 2.0.42, and that the repository has been read-only since it was archived on June 9. A fixed standalone mod_h2 version is therefore not confirmed.
What to do now
- Find every Apache HTTP Server instance and check its version. Anything from 2.4.55 through 2.4.70 is in range.
- Check whether HTTP/2 is enabled by looking for h2 or h2c in the Protocols directive, server-wide and in each virtual host.
- Upgrade to Apache HTTP Server 2.4.71 or later (Apache HTTP Server project), or install your distribution’s fixed package where one exists (see the list above). Version numbers of distribution packages differ from upstream.
- If you cannot patch yet, Wiz advises removing h2 and h2c from the Protocols directive so only
Protocols http/1.1remains. The Hacker News notes that the Apache advisory itself offers no workaround, and that this change also applies to servers using standalone mod_h2 builds. - Note that 2.4.71 also fixes CVE-2026-106023 (mod_md NULL pointer dereference, important) and CVE-2026-109163 (mod_vhost_alias one-byte stack overwrite, low), per the Apache HTTP Server project.
- If you run WordPress, updating WordPress will not help. SecurityWeek reports that Defiant warned the issue sits in the underlying web server.
Update, 14 November 2026
- Sysdig says CISA rates CVE-2026-119618 at 8.1 on CVSS v3.1, and that Amazon, like Red Hat, scores it 9.8. (webflow.sysdig.com)
- Sysdig says that as of November 13 fixes are out for Debian 12 and 13 (2.4.71-1~deb12u1 and 2.4.71-1~deb13u1), Ubuntu 22.04 through 26.10, Alpine and Fedora. Debian DSA-6620-1 fixed trixie on Nov. 12. (webflow.sysdig.com)
- Sysdig lists Red Hat fixes: mod_http2-2.0.26-7.el9_9.1 (RHSA-2026:98981) for RHEL 9 and mod_http2-2.0.29-5.el10_3.1 (RHSA-2026:98978) for RHEL 10, plus separate RHSAs for the 9.x and 10.x EUS and SAP streams. (webflow.sysdig.com)
- Horizon3 says the third-party proof of concept published on November 12, 2026 reproduces heap corruption on 2.4.70 under memory and thread sanitizers and reports a clean result on 2.4.71. It does not demonstrate code execution, and its author is not affiliated with either reporting team. Sysdig says the CVE is not in CISA’s KEV catalog. (horizon3.ai)
- Imperva says Cloud WAF and WAF Gateway are not affected. Cloud WAF sites are onboarded without HTTP/2 by default, and customers who enabled HTTP/2 can stay protected by choosing the ‘HTTP/2 client to Imperva’ option. (imperva.com)
Update, 15 November 2026
- Wordfence says a public site may serve HTTP/2 through a CDN, load balancer or nginx while its Apache origin receives HTTP/1.1, so exposure depends on the protocol at the Apache origin (including any direct or internal route), not on the public site’s HTTP/2 support. It notes AWS Application Load Balancers use HTTP/1.1 to backend targets by default. (wordfence.com)
- Aikido says servers behind a standard HTTP load balancer are not exposed in the usual setup. It also says that as of November 13, 2026 it knew of no reports of exploitation in the wild. (aikido.dev)
- Wordfence says CloudLinux has published affected-product checks and fixed builds for several hosting configurations. (wordfence.com)
- BleepingComputer reports that watchTowr confirmed HTTP/2 must be enabled for exposure (it is off by default) and recommends admins “patch now or drop h2 until you can.” (bleepingcomputer.com)
- Wordfence advises restarting Apache after installing the fixed package and verifying that the origin no longer accepts HTTP/2 if HTTP/2 was disabled as a stopgap. It also says Apache has not published a complete list of parties notified before disclosure. (wordfence.com)
Update, 18 November 2026
- Orca Security says users of the standalone mod_h2 module, for which no fix exists, should migrate to the mod_http2 bundled in Apache HTTP Server 2.4.71. (orca.security)
- Orca Security classifies CVE-2026-119618 as a race condition (CWE-362) that leads to heap memory corruption. (orca.security)
Sources
- Apache HTTP Server project: Apache HTTP Server 2.4 vulnerabilities
- Wiz: Critical RCE Vulnerability in Apache HTTP Server: Everything You Need To Know
- The Hacker News: Critical Apache HTTP/2 Flaw Could Let Unauthenticated Attackers Execute Code Remotely
- SecurityWeek: Apache Patches Critical HTTP Server RCE Found by Anthropic, Google
- CCCS Canada: Apache security advisory (AV26-1159)
- webflow.sysdig.com: HTTPd (CVE-2026-119618): Detecting heap corruption and RCE in Apache HTTP Server mod_http2
- horizon3.ai: CVE-2026-119618 | Apache HTTP Server mod_http2 Race Condition Remote Code Execution Vulnerability
- imperva.com: Critical Apache HTTP/2 Vulnerability (CVE-2026-119618): How Imperva Protects Customers
- wordfence.com: PSA: Critical Apache HTTP/2 Vulnerability: What WordPress Site Owners Should Know
- aikido.dev: Critical Apache HTTP Server vulnerability can allow remote code execution (CVE-2026-119618)
- bleepingcomputer.com: Apache HTTP Server patches critical HTTP/2 remote code execution flaw
- orca.security: CVE-2026-119618: Critical Apache HTTP/2 Race Condition Enables Unauthenticated Remote Code Execution