On November 11, the Apache Software Foundation shipped an urgent fix for its web server. The bug, CVE-2026-119618, sits in the part of Apache that handles HTTP/2. On an affected server, an attacker with no login and no password could send carefully timed requests that corrupt the server's memory and, in the worst case, run their own code on it.
Apache powers a huge share of the web, so this one matters. The good news: it takes about ten minutes to find out whether you are affected, and most servers can be fixed with one command.
We ran these exact checks on our own Ubuntu server the morning after the news broke. The result surprised us a little, and it is the thing most people get wrong about this bug, so we will start there.
Last checked: November 13, 2026.
The short version
| What it is | A race condition in mod_http2 that can corrupt heap memory, possibly leading to remote code execution |
| Affected | Apache HTTP Server 2.4.55 to 2.4.70, with HTTP/2 turned on |
| Fixed in | Apache 2.4.71, and security updates from Ubuntu, Debian, Red Hat and others |
| Exploited yet? | No attacks seen so far, but researchers expect that to change |
| Quick workaround | Turn off HTTP/2 until you can update |
The flaw was found by Anthropic's OSS Scanner and Google Cloud's Vulnerability Research team. Cloud security company Wiz says 64% of the cloud environments it monitors contain a vulnerable Apache install.
"My server says 2.4.58. Am I vulnerable?"
This is the question we had too. Our server runs Ubuntu 24.04, and apache2 -v printed:
Server version: Apache/2.4.58 (Ubuntu) 2.4.58 is inside the affected range, so it looks bad. But Linux distributions rarely jump to a new Apache version in the middle of a release. Instead, they copy the fix into the version they already ship. This is called backporting. The number stays at 2.4.58, and only the package revision at the end changes.
So the version number alone tells you nothing. What you need to know is whether your installed package includes the fix. On Ubuntu and Debian, read the changelog that came with it:
zcat /usr/share/doc/apache2/changelog.Debian.gz | grep -m1 CVE-2026-119618 (Use this rather than apt changelog, which shows the newest package available, not the one you have installed.)
On our server it printed the fix straight away. Ubuntu released it as 2.4.58-1ubuntu8.19, and our automatic security updates had installed it within hours. If you get no output, you are not patched yet.
On Red Hat, AlmaLinux and Rocky Linux, HTTP/2 lives in its own package:
rpm -q --changelog mod_http2 | grep -m1 CVE-2026-119618 Step 1: Is HTTP/2 even turned on?
The bug only matters if Apache is speaking HTTP/2. Two things must both be true: the http2 module is loaded, and the Protocols line includes h2 or h2c.
Check the module first:
# Ubuntu / Debian sudo apache2ctl -M | grep http2 # Red Hat / Alma / Rocky sudo httpd -M | grep http2 If this prints http2_module, the module is loaded. If it prints nothing, HTTP/2 is off and this bug can't reach you. Patch anyway, but you can breathe.
Then look at the protocol setting:
grep -ri "^\s*Protocols" /etc/apache2/ /etc/httpd/ 2>/dev/null A line like Protocols h2 http/1.1 means HTTP/2 is offered to visitors.
On our server, the Protocols h2 h2c http/1.1 line existed, but only in the module's own config file. The module itself was never enabled, so it was never active. A config file being present is not the same as a feature being switched on.
A trap if you use Cloudflare or a CDN
You may find advice to test from outside with curl --http2. If your site sits behind Cloudflare, a CDN or a load balancer, that test talks to them, not to your server. It will say "HTTP/2" even when your own Apache only speaks HTTP/1.1. Always check on the server itself.
Step 2: Install the fix
Ubuntu and Debian:
sudo apt update sudo apt install --only-upgrade apache2 apache2-bin sudo systemctl restart apache2 Red Hat, AlmaLinux, Rocky Linux:
sudo dnf update httpd mod_http2 sudo systemctl restart httpd Built from source: upgrade to Apache 2.4.71. If you use the standalone mod_h2 module from GitHub, note that it is no longer maintained, so move to the module included in httpd 2.4.71.
Docker: pull a 2.4.71 image (for example httpd:2.4.71) and redeploy. Restarting an old container does nothing; the fix only arrives with the new image.
cPanel, Plesk and other control panels: run the panel's own update tool. Their Apache builds are updated through the panel, not through apt or dnf.
Don't skip the restart. Updating the package replaces the files on disk, but the old Apache keeps running from memory until it restarts. After restarting, run the changelog check again to confirm.
Can't update today? Turn HTTP/2 off
If you can't update right now (a change freeze, an old server, a client who has to approve it), switch HTTP/2 off as a stopgap. Your site keeps working over HTTP/1.1.
Ubuntu and Debian:
sudo a2dismod http2 sudo systemctl restart apache2 Red Hat and friends: comment out the LoadModule http2_module line in /etc/httpd/conf.modules.d/10-h2.conf, then restart httpd.
Also change any Protocols h2 http/1.1 line to Protocols http/1.1, so nothing tries to use HTTP/2.
Will visitors notice? Usually not. HTTP/2 makes pages load a little faster when a page pulls in many files, but for most sites the difference is small. If you are behind Cloudflare, visitors still get HTTP/2 or HTTP/3 from Cloudflare, which talks to your server over HTTP/1.1 unless you switched on its "HTTP/2 to Origin" option.
Is this as bad as it sounds?
Honestly, it is serious but not a panic. A few things work in your favor:
- HTTP/2 is off by default in Apache. Many servers never turned it on.
- Exploiting a race condition is hard. The attacker has to win a timing race between requests, and it doesn't work every time. Red Hat notes that its own builds make it much harder still.
- No attacks have been seen at the time of writing.
On the other hand, a public proof of concept already crashes Apache. Even without full code execution, that is an easy way to knock a site offline. And once a fix is public, attackers study it to work out how to exploit the bug. The window between "fixed" and "exploited" keeps getting shorter.
The bigger lesson: let security updates install themselves
Our server was patched before we even read the news, because it installs security updates automatically. That is the cheapest protection a small team can have. On Ubuntu and Debian it takes a minute to set up:
sudo apt install unattended-upgrades sudo dpkg-reconfigure -plow unattended-upgrades Our 30-minute Linux VPS security checklist covers this along with SSH keys, the firewall and Fail2ban. And if you run PHP or Node.js on the same server, our PHP2Shell and Node.js patch guide walks through the same check-and-patch routine for those.
While you are logged in, it is also a good moment to check that your certificate isn't close to expiring with our free SSL certificate checker.
FAQ
What is CVE-2026-119618?
A race condition in Apache's mod_http2 module. Concurrent requests can corrupt the server's heap memory, which can crash Apache and could let an attacker run code with the web server's permissions.
Which Apache versions are affected?
Apache HTTP Server 2.4.55 through 2.4.70, and the standalone mod_h2 module 2.0.8 through 2.0.42, but only when HTTP/2 is enabled. Apache 2.4.71 fixes it.
I'm on Ubuntu with Apache 2.4.58. Do I need 2.4.71?
No. Ubuntu backports the fix into its own 2.4.58 package. Run zcat /usr/share/doc/apache2/changelog.Debian.gz | grep CVE-2026-119618. If the CVE is listed, you are patched. For Ubuntu 24.04 the fixed package is 2.4.58-1ubuntu8.19.
Does turning off HTTP/2 break my site?
No. Browsers fall back to HTTP/1.1 automatically. Pages may load very slightly slower on some sites, and behind a CDN you won't notice any difference.
Is Nginx affected?
No. This bug is in Apache's own HTTP/2 module. Nginx, LiteSpeed and Caddy use different code.
I'm on shared hosting. What should I do?
Your host manages Apache, so there is nothing to install yourself. If you want to be sure, ask support whether CVE-2026-119618 has been patched on your server.
Ten minutes, a changelog check and a restart. If you look after a server running Apache, do it today, before the people studying this patch get there first.
Sources
Originally published on GeekSpark.

