On 11 November 2026 the Apache Software Foundation released Apache HTTP Server 2.4.71. It fixes three security flaws, and one of them is rated critical: a bug in Apache’s HTTP/2 module that the project says can lead to remote code execution. Apache is one of the most widely used web servers, and it runs underneath a huge number of WordPress and Joomla sites on shared hosting, cPanel servers and VPSs.
If you run your own server, this is one to patch this week. If your website sits on shared or managed hosting, the fix is your host’s job, but it’s worth knowing what to ask. This post explains what the flaw is, who is affected and what to do.
What is the flaw?
The critical issue is tracked as CVE-2026-119618. According to the Apache security advisory, it’s a concurrency bug (a race condition) in the assign_headers() function of mod_http2, the module that lets Apache talk HTTP/2 to browsers. Under the right conditions, two threads can end up using the same piece of memory at once, which corrupts the server’s memory and can let an attacker run their own code.
Red Hat’s write-up explains the risk in plain terms: a remote attacker who can reach the web server could run commands on it without logging in, potentially taking over the server, reading or changing data, or knocking it offline. Red Hat also says public research has demonstrated a reliable exploit against a default-configured server with mod_http2 enabled.
The flaw was reported to Apache by Anthropic’s OSS Scanner on 26 October and separately by Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research on 3 November. The fix itself is a one-line change, which is part of why updating is quick.
Which versions are affected?
| Issue | Severity | Affected versions |
|---|---|---|
| CVE-2026-119618: mod_http2 heap corruption and code execution | Critical | Apache 2.4.55 to 2.4.70 (standalone mod_h2 2.0.8 to 2.0.42) |
| CVE-2026-106023: mod_md crash (NULL pointer) | Important | Apache 2.4.30 to 2.4.70 |
| CVE-2026-109163: mod_vhost_alias one-byte buffer overwrite | Low | Apache 2.4.69 and 2.4.70 |
All three are fixed in Apache 2.4.71. For the standalone HTTP/2 module from GitHub, the fix is mod_h2 2.0.43.
The important detail is that the critical bug only affects servers with HTTP/2 switched on. Red Hat notes that servers serving only HTTP/1.1 are not affected. The catch is that HTTP/2 is switched on in a lot of hosting setups, because it makes sites load faster over HTTPS, so don’t assume yours is off.
Linux distributions often ship older Apache version numbers with their own security fixes added, so the number alone doesn’t always tell the full story. Red Hat, for example, says Red Hat Enterprise Linux 8 and earlier are not affected because their mod_http2 predates the vulnerable code, and it rates the flaw Important rather than Critical on RHEL 9 and 10 because of how those builds handle memory. Always go by your distribution’s or control panel’s own advisory.
If you’re on shared or managed hosting
You can’t update Apache yourself on shared hosting, and you don’t need to. Your hosting company manages the server. Wordfence’s advice in its PSA for WordPress site owners is to check your host’s website or announcements to see whether they have already applied the fix. If you can’t find anything, just ask them.
A short, polite support ticket is enough. Something like: “Has Apache on my server been updated to 2.4.71, or patched for CVE-2026-119618?” A good host will be able to answer that quickly. If your site runs on nginx or LiteSpeed rather than Apache, this particular bug, which is in Apache’s own HTTP/2 module, isn’t the one to worry about, but it’s still worth checking that your host keeps its web server up to date.
If you run a cPanel server
cPanel’s Apache comes from EasyApache 4 rather than the operating system. cPanel has published an advisory saying EasyApache 4 v25.96 includes ea-apache24 2.4.71-1, which contains the upstream fix. Its steps are:
- Log in to the server over SSH.
- Run
/scripts/update-packages. cPanel warns this may briefly restart Apache, so there could be a short interruption. - Confirm the installed version with
dnf list installed ea-apache24on CloudLinux, AlmaLinux or Rocky Linux. It should show 2.4.71-1 or newer.
If you have automatic updates turned on in WHM, it may already have been installed overnight, but check rather than assume. You can also see the running version with httpd -v.
If you run Plesk or a plain Linux server
On Plesk, and on any server without a control panel, Apache comes from the operating system’s own packages, so the fix arrives through normal system updates. CloudLinux, for example, says the system Apache on CloudLinux 9 and 10 needs the mod_http2 package updated and Apache restarted, the system Apache on CloudLinux 7 and 8 is not affected, and Ubuntu released a fixed apache2 package for Ubuntu 22.04 on 12 November.
In practice that means running your usual update command (dnf update or apt update && apt upgrade), restarting Apache, and then checking your distribution’s security page for CVE-2026-119618 to confirm the fixed package version.
Can’t update yet? Turn HTTP/2 off for now
If you can’t patch straight away, the published workaround is to stop Apache offering HTTP/2. In your Apache configuration, remove h2 and h2c from the Protocols line so it reads Protocols http/1.1, then restart Apache. On a cPanel server you can switch off mod_http2 in WHM’s EasyApache 4 profile instead.
Your site will keep working over HTTP/1.1. It may be a little slower to load, so switch HTTP/2 back on once the update is in.
Why server updates matter as much as WordPress updates
Most website owners think about security in terms of WordPress core, plugins and themes. Those matter, but the software underneath matters just as much. In the last few weeks we’ve seen critical PHP flaws and root-level bugs in cPanel and Plesk, and now a critical Apache bug. Any one of them can put every site on a server at risk, however well each site is kept up to date.
That’s why the choice of host matters. A good host patches the web server, PHP and the control panel quickly and tells customers when it has. If you manage your own server, it’s worth setting up automatic security updates and keeping an eye on advisories. If you’re still deciding how to run your hosting, my comparison of cPanel and Plesk covers how each one handles updates.
Sources
- Apache HTTP Server Project: Apache HTTP Server 2.4 vulnerabilities
- Red Hat: CVE-2026-119618
- cPanel: Vulnerability CVE-2026-119618 in Apache HTTP Server mod_http2
- CloudLinux: critical Apache mod_http2 flaw CVE-2026-119618
- NVD: CVE-2026-119618
Need help?
I manage hosting and servers for small businesses in Milton Keynes and across the UK. If you’re not sure whether your server is patched, or you’d like me to check it for you, get in touch.



