A critical remote code execution flaw in Apache HTTP Server’s mod_http2 module, tracked as CVE-2026-119618, was disclosed on November 11, 2026 — if you run Apache with HTTP/2 enabled, this one belongs at the top of your patch queue.
What happened in CVE-2026-119618
On November 11, 2026, the Apache Software Foundation released Apache HTTP Server 2.4.71, fixing a single critical vulnerability:
- CVE-2026-119618
Red Hat rates the flaw 9.8 CVSS upstream, with a reliable exploit already demonstrated. The bug was found independently by two parties: Anthropic’s OSS Scanner, which reported it to the Apache security team on October 26, 2026, and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research, who reported it on their own on November 3, 2026.
Root cause
The flaw sits in a function called assign_headers() inside mod_http2. It is a concurrency bug, classified as CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization): two parts of the module can touch the same piece of memory at the same time without proper locking. On a server handling concurrent HTTP/2 streams, that race condition corrupts the heap — and heap corruption in a network-facing worker process is a direct path to remote code execution.
Because the race lives inside HTTP/2 stream header handling rather than in any specific application code, any Apache server with HTTP/2 enabled is exposed, regardless of what the backend application does with the request afterward. The attack requires no authentication.
Who is affected
- Apache HTTP Server 2.4.55 through 2.4.70, and the related mod_h2 GitHub project versions 2.0.8 through 2.0.42.
- Only servers that have
mod_http2loaded and HTTP/2 actually enabled on at least one vhost are reachable. A server offering HTTP/1.1 only does not reach the vulnerable code, even if the module is installed. - Red Hat notes that on RHEL 9 and 10, each HTTP/2 stream is allocated from a separate memory allocator, which raises exploitation difficulty — hence those distros rate the issue “Important” rather than “Critical” despite the 9.8 upstream score. Treat that as reduced difficulty, not reduced severity.
Patched version (upstream Apache)
| Component | Patched version |
|---|---|
| Apache HTTP Server | 2.4.71 |
| mod_h2 (GitHub project) | 2.0.43+ |
Important: most enterprise and LTS distributions backport the security fix into their existing package version rather than bumping to the upstream version number above, and several ship the fix inside a separate mod_http2 package rather than httpd itself. A httpd -v or apache2 -v that still shows a pre-2.4.71 string does not mean you’re unpatched — and one that does show 2.4.71 does not guarantee mod_http2 was updated alongside it. Check the package changelog, not the version banner.
Affected status by distribution
| Distribution | Status | Notes |
|---|---|---|
| RHEL / Oracle Linux / AlmaLinux / Rocky Linux 7 | Not affected | Predates the vulnerable code entirely |
| RHEL / Oracle Linux / AlmaLinux / Rocky Linux 8 | Not affected | mod_http2 predates version 2.0.8 |
| RHEL 9 | Affected (Important) — fixed | RHSA-2026:98981, mod_http2-2.0.26-7.el9_9.1 |
| RHEL 10 | Affected (Important) — fixed | RHSA-2026:98978, mod_http2-2.0.29-5.el10_3.1 |
| Oracle Linux 9 / 10 | Affected — tracks RHEL base | Confirm the Oracle-specific ELSA number directly at linux.oracle.com/cve/CVE-2026-119618.html rather than assuming parity with the RHSA above |
| AlmaLinux / Rocky Linux 9 / 10 | Affected — rebuild RHEL errata | Packages were not yet published on some mirrors as of the morning of November 12; check each project’s own errata page for availability |
| Debian unstable (sid) | Fixed | apache2 2.4.71-1 |
| Debian 12 (bookworm) / 13 (trixie) | Affected — fix status conflicting between sources at time of writing | Check security-tracker.debian.org/tracker/CVE-2026-119618 directly |
| Ubuntu | Affected — module present, not loaded by default | Check ubuntu.com/security/CVE-2026-119618 for the current advisory |
| Amazon Linux 2 / 2023 / 2027 Preview | Affected — fix pending | At time of writing |
How to update, by distribution
RHEL, Oracle Linux, AlmaLinux, Rocky Linux (9, 10)
sudo dnf clean metadata
sudo dnf upgrade mod_http2 httpd
sudo systemctl restart httpdThe fix lands in the mod_http2 package specifically — upgrading httpd alone is not sufficient to confirm coverage. List pending security errata to confirm it’s queued:
sudo dnf updateinfo list security | grep -i http2Debian
sudo apt update
sudo apt install apache2
sudo systemctl restart apache2Ubuntu
sudo apt update
sudo apt upgrade
sudo systemctl restart apache2Verifying the patch actually landed
Do not trust the version string alone — enterprise distros routinely backport this kind of fix into an existing package build number.
# Check the changelog for the CVE ID directly
rpm -q --changelog mod_http2 | grep -i 'CVE-2026-119618'
rpm -q --changelog httpd | grep -i 'CVE-2026-119618'
# Debian/Ubuntu equivalent
apt changelog apache2 | grep -i 'CVE-2026-119618'Cross-reference the installed package’s name-version-release against your distro’s own advisory page for the exact “fixed in” build — Red Hat’s RHSA, Debian’s security tracker, or Ubuntu’s USN each name the precise version, which is more reliable than inferring patch status from the banner httpd -v prints.
Mitigating CVE-2026-119618 if you can’t patch immediately
Because the vulnerable code only executes for HTTP/2 traffic, disabling the module closes the hole completely until you can patch.
Debian / Ubuntu:
sudo a2dismod http2
sudo systemctl restart apache2RHEL / Oracle Linux / AlmaLinux / Rocky Linux / CentOS — open /etc/httpd/conf.modules.d/10-h2.conf (and 10-proxy_h2.conf if present) and comment out the LoadModule http2_module line, then restart:
sudo systemctl restart httpdThis is a complete, not partial, mitigation for this specific flaw — a server that no longer negotiates HTTP/2 does not reach the vulnerable assign_headers() code path at all. Unlike mitigations that only cover known exploitation techniques, disabling the module removes the entire attack surface. The tradeoff is losing HTTP/2’s connection multiplexing and header compression benefits until you patch and re-enable it — plan to re-enable the module once your mod_http2 package is confirmed updated, rather than leaving HTTP/2 off indefinitely.
Summary: closing out CVE-2026-119618
- Patch to Apache HTTP Server 2.4.71 (upstream) or your distro’s backported
mod_http2build. - RHEL/Oracle Linux/AlmaLinux/Rocky Linux 7 and 8 are not affected; 9 and 10 are, and the fix ships in the
mod_http2package, not justhttpd. - If you can’t patch yet, disable
mod_http2entirely — this fully closes the hole, unlike partial mitigations for other classes of bugs. - Verify the fix against your distro’s changelog and advisory page, not the version string alone.
Let us know in the comments if you need help auditing your Apache fleet for this one.
Sources
- Apache HTTP Server 2.4.71 Fixes Critical mod_http2 Heap Corruption (CVE-2026-119618)
- Apache Patches Critical HTTP Server RCE Found by Anthropic, Google — SecurityWeek
- Critical Vulnerability in Apache HTTP Server Could Allow Remote Code Execution via HTTP/2 — BigGo Finance
- CVE-2026-119618: Vulnerability Details — Analysis & Fix
- Critical Apache HTTP/2 Flaw Could Let Unauthenticated Attackers Execute Code Remotely
- CVE-2026-119618 — OpenCVE
- CVE-2026-119618: Critical Apache HTTP/2 RCE — SOC Prime
- Apache 2.4.71 Closes a Critical HTTP/2 Flaw in mod_http2
- Apache HTTP Server HTTP/2 RCE, Fixed in 2.4.71
- Apache Patches Critical HTTP/2 Flaw Allowing Remote Code Execution on Web Servers