The Apache HTTP Server project rates CVE-2026-119618 critical: a thread-safety bug in mod_http2 that “can lead to RCE”. It affects httpd 2.4.55 through 2.4.70, and the standalone mod_h2 module from 2.0.8 through 2.0.42. The fix shipped in httpd 2.4.71 on 11 November.
What the bug is
HTTP/2 lets one client send many requests at once over a single connection, and mod_http2 handles them on worker threads. Red Hat’s bulletin explains the flaw: a worker thread can write into memory owned by the connection thread through a shared allocator that has no lock. That corrupts the server’s memory, and a crafted sequence of concurrent HTTP/2 requests can turn it into code execution in the httpd process. No login is needed; the attacker only has to reach the HTTP/2 port.
Red Hat’s CVE page says public research has shown a reliable exploit against a default-configured server with mod_http2 enabled. The upstream fix, commit 824beab, is a one-line change in assign_headers().
Apache credits two independent finders: Anthropic’s OSS Scanner, which reported it on 26 October, and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research, who reported it on 3 November. We covered the scanner program earlier.
Who is affected
Only servers with HTTP/2 turned on: h2 or h2c in a Protocols directive, with mod_http2 loaded. Servers that serve only HTTP/1.1 are not affected. A quick check from Red Hat’s bulletin:
curl -kI --http2 https://your-host/
# "HTTP/2 200" on the first line means HTTP/2 is on
grep -ri "Protocols" /etc/httpd/conf/ /etc/httpd/conf.d/
On Debian and Ubuntu the config lives under /etc/apache2/ instead.
Distro status, checked 13 November:
- Debian. Fixed in 2.4.71 for bookworm and trixie security (DSA-6620-1, DLA-4902-1) and in sid, per the security tracker.
- Ubuntu. Priority High, fixed packages listed for 20.04 through 26.10 on the CVE page, with 20.04 through Ubuntu Pro. Ubuntu notes that newer
mod_http2code was backported, which is why releases such as 22.04, on httpd 2.4.52, get a fix too. Do not rule a server out by its httpd version alone. - Red Hat. Critical overall, but rated Important on RHEL 9 and 10 because their
mod_http2gives each stream its own allocator. RHEL 8 and earlier are not affected. - Containers. The official
httpd:2.4.71images, including Alpine, were pushed to Docker Hub on 13 November. Rebuild anything based on older tags.
If you built the standalone mod_h2 from GitHub, note that its repository has been archived since June and has no release after 2.0.42. Move to the module bundled with httpd 2.4.71.
If you cannot patch today
Remove h2 and h2c from every Protocols line so it reads Protocols http/1.1, then restart httpd. Browsers and API clients fall back to HTTP/1.1. Red Hat warns of slower page loads and more bandwidth without HTTP/2 multiplexing, and says the eventual fix does not require turning HTTP/2 off.
Why this matters
Apache httpd sits in front of a lot of production traffic, and this is an unauthenticated network bug with a reliable exploit, according to Red Hat. Fixed packages and container images are already out, so the gap between disclosure and attack is the time you take to roll them. It is also the second server-side patch-now note this week, after the MongoDB pre-auth crash, and one where an AI scanner and a human research team found the same bug a week apart.
Update, 20 November 2026: VMware Aria Operations and HCX are affected, with no patch yet
Broadcom published VMSA-2026-0010 on 19 November. It says the Apache httpd shipped in VMware Cloud Foundation Operations 9.x, VMware Aria Operations 8.18.x (and 5.x in VCF) and VCF Operations HCX 9.1.x contains this mod_http2 bug, rated 9.8, and that an attacker with network access to Aria Operations or HCX “may exploit this issue to execute arbitrary code”. Every row in its response matrix says “Patch pending”.
The workaround is to turn off HTTP/2. For Aria Operations and VCF Operations, Broadcom’s KB463005 offers a script that checks each node’s Apache version and comments out mod_http2. Broadcom says collectors, agents and the API are not affected, but “the UI may feel slower”. It also warns that each upgrade replaces the Apache config and turns HTTP/2 back on, so re-check after every upgrade until a fixed Apache ships. For HCX Manager, KB463022 provides a block-http2.sh script and says there is no functional impact on running migrations.
Broadcom’s portfolio note says it reviewed its VMware products and none are affected except Aria Operations and VCF Operations HCX. The advisory does not mention exploitation.
Update, 21 November 2026: Singapore warns of active exploitation
Singapore’s Cyber Security Agency issued an alert on 17 November saying CVE-2026-119618 “is reportedly being actively exploited, and a proof-of-concept exploit is publicly available”. It tells administrators of httpd 2.4.55 to 2.4.70 with mod_http2 enabled to update immediately. CSA does not say who is exploiting it or where the reports come from, and it scores the bug 8.1 under CVSS 3.1. CISA’s Known Exploited Vulnerabilities feed, last updated 20 November, does not list it yet. Broadcom’s VMSA-2026-0010 still showed “Patch pending” for Aria Operations when we checked on 21 November, so the HTTP/2 workaround above remains the only option there.

The Campfire
CommentsThanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.
Add a comment