Apache has patched a critical bug in its HTTP Server that could let an attacker run code on your web server without logging in. It’s tracked as CVE-2026-119618, and Anthropic’s automated scanner and Google’s researchers found it independently. This guide explains the flaw in plain terms, then shows you how to check whether your server is affected and how to patch it on Ubuntu, Debian, RHEL-style systems and Docker. There’s also a quick fix if you can’t update today.
Everything here is as of 14 November 2026, from Apache’s security page, Red Hat, Ubuntu and Debian’s trackers, and reporting by SecurityWeek and Wiz.
What the bug is
The flaw is in mod_http2, the Apache module that handles HTTP/2 traffic. HTTP/2 lets a browser send many requests at once over one connection, and Apache handles those requests on several threads. Red Hat explains that, because of a thread-safety mistake, one thread can write into memory that belongs to another. An attacker can use that memory corruption to run commands on the server with the web server’s privileges.
The key facts:
| Item | Detail |
|---|---|
| CVE | CVE-2026-119618 |
| Apache rating | Critical (Red Hat CVSS 3 score: 9.8) |
| Affected Apache versions | 2.4.55 through 2.4.70 |
| Affected standalone mod_h2 | 2.0.8 through 2.0.42 (from GitHub) |
| Fixed in | Apache HTTP Server 2.4.71, released 11 November 2026 |
| Who’s exposed | Only servers with HTTP/2 (h2 or h2c) turned on |
| Found by | Anthropic’s OSS Scanner (reported 26 October) and Google Cloud Vulnerability Research (3 November) |
Is it being exploited? Reports differ. Wiz said on 11 November that no exploit was public and it had seen no attacks. Red Hat’s page says “public research has demonstrated a reliable exploit” against a default server with mod_http2 enabled, but doesn’t say which research. SecurityWeek found a public proof of concept that crashes Apache but doesn’t show code execution. Treat it as urgent either way.
How widespread? Wiz says 64% of the cloud environments it sees have resources running affected versions, and 51% have exposed instances. It adds that these numbers don’t account for whether HTTP/2 is actually on.
The 2.4.71 release also fixes two smaller bugs: CVE-2026-106023, a crash in mod_md rated important, and CVE-2026-109163, a one-byte overflow in mod_vhost_alias rated low.
What you need
- SSH access to your server with sudo rights (see our guide to setting up SSH keys if you don’t have this yet)
- About 10 minutes and a short restart window for Apache
If you run WordPress or another app on shared hosting, you can’t fix this yourself. Wordfence maker Defiant pointed out that WordPress updates can’t solve it, because the bug is in the web server underneath. Ask your host whether its Apache servers have been patched.
Step 1: Check your Apache version
apachectl -v
On Debian and Ubuntu the command may be apache2 -v, and on RHEL-style systems it may be httpd -v. You’ll see something like:
Server version: Apache/2.4.58 (Ubuntu)
Don’t stop at this number. Linux distributions backport fixes without changing the main version. Ubuntu, for example, fixed the bug in its 2.4.58 package for 24.04, and its notes say even its older 2.4.52 and 2.4.41 builds were affected, because newer mod_http2 code had been backported into them. On a distro, the package version in Step 4 is what counts.
Step 2: Check if HTTP/2 is turned on
First, see whether the module is loaded:
apachectl -M | grep http2
If this prints http2_module (shared), the module is loaded. Then look for a Protocols line that enables it:
sudo grep -Rni "^\s*Protocols" /etc/apache2/ /etc/httpd/ 2>/dev/null
A line such as Protocols h2 http/1.1 or Protocols h2 h2c http/1.1 means HTTP/2 is on.
You can also test from any machine. Replace example.com with your domain:
curl -sI --http2 https://example.com -o /dev/null -w '%{http_version}\n'
If it prints 2, your site answers over HTTP/2 (make sure Apache is the server answering, not a CDN or proxy in front of it). If it prints 1.1, HTTP/2 isn’t on at that address.
Step 3: Patch on Ubuntu or Debian
sudo apt update
sudo apt install --only-upgrade apache2
sudo systemctl restart apache2
Fixed package versions, according to Ubuntu’s and Debian’s security trackers:
| Release | Fixed apache2 package |
|---|---|
| Ubuntu 26.04 LTS | 2.4.66-2ubuntu2.8 |
| Ubuntu 24.04 LTS | 2.4.58-1ubuntu8.19 |
| Ubuntu 22.04 LTS | 2.4.52-1ubuntu4.27 |
| Ubuntu 20.04 LTS | 2.4.41-4ubuntu3.23+esm11 (needs Ubuntu Pro) |
| Debian 13 (trixie) | 2.4.71-1~deb13u1 |
| Debian 12 (bookworm) | 2.4.71-1~deb12u1 |
Ubuntu 18.04 and older are listed as not affected.
Step 4: Confirm the package version
apt-cache policy apache2
The “Installed” line should match or be newer than the fixed version for your release in the table above.
Step 5: Patch on RHEL, Rocky, Alma or CentOS Stream
On Red Hat Enterprise Linux the fix ships in the separate mod_http2 package:
sudo dnf update mod_http2 httpd
rpm -q mod_http2
sudo systemctl restart httpd
Red Hat released fixes for RHEL 9 and RHEL 10 on 11 November and rates them Important rather than Critical. On those versions each HTTP/2 stream uses its own memory allocator, which makes the bug much harder to exploit. RHEL 8 and earlier aren’t affected, because their mod_http2 doesn’t contain the faulty code. Rebuilds such as Rocky and AlmaLinux usually follow Red Hat’s updates, so check your distribution’s advisory.
Step 6: Update Docker containers
If you run the official httpd image, pull the latest and check what’s inside:
docker pull httpd:2.4
docker run --rm httpd:2.4 httpd -v
Look for Apache/2.4.71 or later, then rebuild and redeploy any images built on it. A running container doesn’t update itself.
Quick fix if you can’t patch today: turn off HTTP/2
Red Hat, Wiz and SecurityWeek all say servers that only speak HTTP/1.1 aren’t vulnerable. Set the Protocols line to HTTP/1.1 only:
Protocols http/1.1
On Debian and Ubuntu you can also disable the module:
sudo a2dismod http2
Then test the config and restart:
sudo apachectl configtest
sudo systemctl restart apache2
Use httpd instead of apache2 on RHEL-style systems. Run the curl test from Step 2 again. It should now print 1.1. HTTP/1.1 can be slightly slower for busy sites, so turn HTTP/2 back on once you’ve patched.
Common errors and fixes
Command not found. If apachectl isn’t found, try apache2ctl (Debian/Ubuntu) or the full path /usr/sbin/apachectl. Your server may also be running Nginx or another web server, in which case this bug doesn’t apply to it.
Syntax error after editing Protocols. Each Protocols line takes a space-separated list. Check for leftover characters, then run sudo apachectl configtest again before restarting.
curl still shows HTTP/2 after you disabled it. A CDN or load balancer in front of Apache may be talking HTTP/2 to visitors. That’s fine, because the risk is HTTP/2 reaching Apache. Run the test against the server directly, or check its config.
Ubuntu 20.04 shows no update. The fix for 20.04 comes through Ubuntu Pro’s ESM repositories. Enable Ubuntu Pro (Ubuntu says it’s free for personal use) or upgrade to a supported release.
apt says apache2 is already the newest version. Run sudo apt update first. If it still doesn’t change, check that the security repository is in your sources list.
Wrap-up
If your Apache server speaks HTTP/2, update it now. On a distro, go by the package version rather than Apache’s own number. If you can’t update straight away, switch to HTTP/1.1 until you can. Credit where it’s due: Anthropic’s automated scanner reported the bug about a week before Google’s researchers independently found it. For more on keeping software patched, read our explainer on Chrome zero-days.
Sources
Links last checked on 15 November 2026.





Write a response