Apache’s Critical mod_http2 Flaw Is Fixed in 2.4.71, but VMware Has Only a Workaround for Its Own Products
Apache fixed a critical remote code execution flaw in mod_http2 on 11 November. Linux distributions have patches, but Broadcom's VMware operations tools have a manual workaround only. What to check and in what order.

Apache’s security team has fixed a critical remote code execution flaw in the HTTP/2 module of its web server, and on Friday 20 November VMware said it has no patch yet for the products that bundle it. The flaw, CVE-2026-119618, sits in mod_http2 and affects Apache HTTP Server 2.4.55 through 2.4.70. The fix shipped in 2.4.71 on 11 November. Debian, Ubuntu and Red Hat have all issued their own fixed packages. Broadcom’s VMware Cloud Foundation Operations, Aria Operations and HCX Manager are the exception: Broadcom’s advisory VMSA-2026-0010 gives a manual workaround for them and nothing else for now.
If you run Apache yourself, the job is a package update and a two-minute check of whether you were exposed. If you run VMware’s operations tooling, the job is a change to a management appliance that Broadcom has asked you to make by hand. Both are covered below.
#What Apache says about the flaw
Apache’s own vulnerability page describes CVE-2026-119618 as “heap corruption and RCE in assign_headers” and rates it critical. The cause is a concurrency bug: code in mod_http2 uses a shared resource without proper synchronisation, and the advisory says that can lead to remote code execution. It affects Apache HTTP Server from 2.4.55 through 2.4.70, and the standalone mod_h2 module that Apache publishes on GitHub from 2.0.8 through 2.0.42. The page credits two finders: Anthropic’s OSS Scanner, which reported it to Apache on 26 October, and Anthony Weems and Simon Scannell of the Google Cloud Vulnerability Research team, who reported it on 3 November. The fix went into 2.4.x on 11 November with the 2.4.71 release.
That release is a bigger one than the headline flaw suggests. Apache lists three fixes in 2.4.71: the critical mod_http2 bug, an important-rated NULL pointer problem in mod_md (CVE-2026-106023) that can crash a child process, and a low-rated stack buffer overwrite in mod_vhost_alias (CVE-2026-109163) that affects only 2.4.69 and 2.4.70.
Red Hat’s own assessment is blunter than a version range. Its Product Security team rates the flaw Critical, says it allows unauthenticated remote code execution, and writes that “public research has demonstrated a reliable exploit against a default-configured server with the mod_http2 module enabled.” It describes the root cause as a thread-safety flaw in how mod_http2 handles concurrent HTTP/2 requests, where a worker thread writes into memory owned by the connection thread through a shared allocator that has no locks. Red Hat rates Red Hat Enterprise Linux 9 and 10 as Important rather than Critical and says RHEL 8 and earlier are not affected, since mod_http2 versions before 2.0.8 do not contain the affected code. We have not found any vendor or authority saying the flaw is being exploited in attacks, and it was not in CISA’s Known Exploited Vulnerabilities catalogue (version 2026.11.20) when we checked on Saturday 21 November. Red Hat’s reference to public research is the reason we would not wait for that to change.
#Where the Linux distributions stand
Version numbers mislead here, and the distributions say so themselves. Ubuntu’s security team notes that newer versions of the HTTP/2 module have been backported into its stable releases, so the upstream version range does not map cleanly onto Ubuntu’s package versions, and a fixed Ubuntu server can still print an old Apache version string. Check the package revision, not the output of apache2 -v.
Ubuntu published USN-9090-1 on 12 November and rates the flaw High. Its fixed builds are 2.4.66-2ubuntu2.8 on 26.04 LTS, 2.4.58-1ubuntu8.19 on 24.04 LTS and 2.4.52-1ubuntu4.27 on 22.04 LTS. For 20.04 the fix is in the Ubuntu Pro (ESM) channel, as 2.4.41-4ubuntu3.23+esm11, and 18.04 is listed as not affected. Debian’s tracker shows the fix as 2.4.71-1~deb13u1 for trixie (DSA-6620-1) and 2.4.71-1~deb12u1 in the bookworm security archive (DLA-4902-1), while the plain bookworm package still on 2.4.68-1~deb12u1 is marked vulnerable. In other words, a Debian 12 machine that has not pulled from the security archive is still exposed. Red Hat points to a security bulletin, RHSB-2026-017, for its mitigation procedure.
#VMware’s operations tooling has a manual fix only
The Register reported on Friday that VMSA-2026-0010 warns that VMware Cloud Foundation, Aria Operations and VCF Operations HCX use the vulnerable Apache code, carries a 9.8 severity rating, and has no patched release yet. The Register says VMware plans to ship new versions with a fixed Apache, and that for now it offers workarounds that disable HTTP/2. This is a separate advisory from VMSA-2026-0009, the vCenter authentication bypass we covered on Thursday, which has fixed builds. Teams patching vCenter this weekend should not assume that work also covers the operations appliances.
Broadcom’s knowledge base articles set out the two workarounds. For VMware Aria Operations 8.18.x and VMware Cloud Foundation Operations 9.x (article 463005), Broadcom supplies a script, cve-2026-119618_v2.sh, that checks every analytics node in a cluster and applies or reverts the change. It connects to each primary, primary replica, data and witness node over SSH as root, so you have to enable SSH on those nodes first. Its --check mode prints the Apache version, whether the fix is present and whether HTTP/2 is on for each node, and flags the ones that are affected. Broadcom says Cloud Proxy nodes are not affected and do not need the change. For VCF Operations HCX Manager 9.1.x (article 463022), Broadcom’s fix is to disable the h2 protocol in the Apache configuration with a script called block-http2.sh, which backs up the configuration first. Broadcom says the change has no functional impact and will not affect ongoing migrations or network extensions. It asks you to take a backup or snapshot of the appliance first, and says to confirm afterwards that curl --http2 against ports 443 and 9443 falls back to HTTP/1.x.
#Our view: a weekend job, not a drill
We would rate this a patch-this-week item rather than an emergency, with two exceptions. The first is any Apache server that faces the internet with HTTP/2 switched on. Red Hat’s wording ties the demonstrated exploit to exactly that setup, and the finders reported the bug to Apache weeks ago, so the fix has been public in source form since 11 November. The second is any VCF Operations or HCX appliance reachable by people you do not trust, because there is no vendor patch to install and the exposure lasts until Broadcom ships one. We think the sensible default for the VMware appliances is to apply the workaround now, since Broadcom says the HCX change has no functional impact and the script on the operations side is reversible.
The pattern is worth noticing. Two widely used web servers have now had serious HTTP/2 flaws in the same week, counting the nginx HTTP/2 flaws we covered on 19 November. We would not call it a trend on that evidence alone, but it does mean the HTTP/2 module is the first place to look when you are asked to reduce a web server’s exposure. Many sites turned it on years ago for speed, and a reverse proxy or content delivery network in front of the server usually gives the browser HTTP/2 anyway, so switching it off between the proxy and the origin often costs nothing.
We expect Broadcom to ship fixed appliance builds within weeks, not months, because the upstream fix is a version bump, but that is our expectation, not a date Broadcom has given. What would prove us wrong is a revised VMSA that names a later release for HCX or Operations.
#What to check, in order
- List your Apache servers, including the ones nobody remembers: control panels, appliances and containers that bundle httpd. The package manager will not find the ones that carry their own copy.
- On each, check whether HTTP/2 is loaded and offered. Run
apachectl -M(orapache2ctl -Mon Debian and Ubuntu) and look forhttp2_module, then search the configuration for aProtocolsline containingh2orh2c. A server that never loads the module is not running the affected code. - Update from your distribution’s security channel and confirm the package revision against the lists above. On Debian 12, make sure the security archive is enabled.
- Where you cannot update today, switch HTTP/2 off by removing
h2andh2cfromProtocolsand reloading Apache, then test withcurl --http2that the server answers over HTTP/1.1. - For VMware: confirm which product and version you run against VMSA-2026-0010, snapshot the appliance, run Broadcom’s script in check mode and then apply it. Keep the revert option in mind, and add the appliance to your list to patch when Broadcom releases a fixed version.
- Check the web server logs for unusual HTTP/2 connection resets or worker crashes since 11 November. We have no published indicators for this flaw, so treat this as general hygiene.
Small businesses are most likely to meet this flaw through a web hosting account or a self-managed website server rather than through VMware. If your site is on shared hosting, your hosting provider applies the Apache update, and the useful question for them is whether they have installed the 2.4.71 fix or their distribution’s equivalent. If you run your own server and nobody has logged in since the site went live, the checks above are the whole job.
Evidence trail
Sources and verification
Primary documentation and external technical references used in this article.
- 01Apache HTTP Server 2.4 vulnerabilities, fixed in 2.4.71httpd.apache.org
- 02Red Hat: CVE-2026-119618access.redhat.com
- 03Ubuntu: CVE-2026-119618ubuntu.com
- 04Debian security tracker: CVE-2026-119618security-tracker.debian.org
- 05Broadcom: workaround for CVE-2026-119618 on VCF Operationsknowledge.broadcom.com
- 06Broadcom: workaround for CVE-2026-119618 on VCF Operations HCX Manager 9.1.xknowledge.broadcom.com
- 07The Register: Flaws in VMware and KVM need attentiontheregister.com
- 08CISA Known Exploited Vulnerabilities cataloguecisa.gov
About this page
Credited to
Dates
Published
Corrections
No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.
More news
All news


Artificial IntelligenceAmazon Says Suspected Chinese Attackers’ AI Agents Found a MONAI Label Zero-Day on Their Own
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Get new fixes by email.
New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.
Comments
Add a thoughtful note on Apache’s Critical mod_http2 Flaw Is Fixed in 2.4.71, but VMware Has Only a Workaround for Its Own Products. Comments are checked for spam and held for moderation before appearing.