CVE-2026-119618 is a race in Apache’s mod_http2 that corrupts the heap while it assigns response headers. The Apache team rates it critical because it leads to remote code execution. Upstream fixed it in httpd 2.4.71 on 11 November 2026, but on RHEL-family distros and Ubuntu you won’t see that number. There the fix arrives as a backported mod_http2 or apache2 build, while Debian ships 2.4.71 itself. A day later Red Hat, AlmaLinux and Debian had shipped one, while Rocky Linux and Ubuntu had not.
Your server is exposed only when three things line up: httpd is 2.4.55 through 2.4.70 (or older with a backported mod_http2), mod_http2 is loaded, and a Protocols line offers h2 or h2c. So check those three, patch where a package exists, and switch HTTP/2 off everywhere else until one lands. For a distro whose CVE-2026-119618 patch status still shows no fixed build, the linked guide turns HTTP/2 off on Ubuntu, Debian and Rocky Linux and shows how to prove it took. We tested these checks and fixes on Ubuntu 26.04 and 24.04, Debian 13 and 12, Rocky Linux 10, 9 and 8, and AlmaLinux 10 and 9 in November 2026, plus the Ubuntu 22.04 package. The RHEL steps come from Red Hat’s errata and were not run on a subscribed RHEL host.
Check whether CVE-2026-119618 affects your server
The Apache httpd 2.4 advisory limits the bug to mod_http2 in releases 2.4.55 to 2.4.70, plus the standalone mod_h2 module from 2.0.8 to 2.0.42. A server that never speaks HTTP/2 can’t reach the vulnerable code, which is why the version alone doesn’t settle it. You’re exposed only if all of these hold:
- httpd 2.4.55 to 2.4.70, or mod_http2 2.0.8 or later without the fix
http2_modulein the loaded module listh2(TLS) orh2c(cleartext) in an activeProtocolsline
The distros don’t agree on the second and third points, and that matters more than the version. On Ubuntu and Debian, a2enmod http2 turns on a module config that already says Protocols h2 h2c http/1.1, so loading the module is enough. On Rocky and AlmaLinux, httpd pulls in mod_http2 as a weak dependency, so a normal install loads it, but the stock config has no Protocols line and serves HTTP/1.1 until someone adds h2. Here is where each family stood when we checked on 12 November 2026:
| Distro | Newest package in the repo | Status | Fixed package |
|---|---|---|---|
| RHEL 10 | mod_http2 2.0.29-5.el10_3.1 (not lab-tested) | Fixed (RHSA-2026:98978) | mod_http2-2.0.29-5.el10_3.1 |
| RHEL 9 | mod_http2 2.0.26-7.el9_9.1 (not lab-tested) | Fixed (RHSA-2026:98981) | mod_http2-2.0.26-7.el9_9.1 |
| AlmaLinux 10 | mod_http2 2.0.29-4.el10_2.2.alma.1 | Fixed, no advisory | mod_http2-2.0.29-4.el10_2.2.alma.1 |
| AlmaLinux 9 | mod_http2 2.0.26-6.el9_8.2.alma.1 | Fixed, no advisory | mod_http2-2.0.26-6.el9_8.2.alma.1 |
| Rocky Linux 10 and 9 | mod_http2 2.0.29-4.el10_2.2, 2.0.26-6.el9_8.2 | Vulnerable, rebuild pending | none yet |
| RHEL 8 and its rebuilds | mod_http2 1.15.7 | Not affected | not needed |
| Ubuntu 26.04 | apache2 2.4.66-2ubuntu2.7 | Vulnerable, no USN | none yet |
| Ubuntu 24.04 | apache2 2.4.58-1ubuntu8.18 | Vulnerable, no USN | none yet |
| Ubuntu 22.04 | apache2 2.4.52-1ubuntu4.26 (mod_http2 2.0.42 backport) | Vulnerable, no USN | none yet |
| Debian 13 | apache2 2.4.71-1~deb13u1 | Fixed (DSA-6620-1) | apache2 2.4.71-1~deb13u1 |
| Debian 12 | apache2 2.4.71-1~deb12u1 (bookworm-security) | Fixed package, no DSA or DLA, tracker still says vulnerable | apache2 2.4.71-1~deb12u1 |
RHEL’s fixed builds carry el9_9 and el10_3 tags while Rocky and Alma sit on 9.8 and 10.2, which is likely why Alma built its own .alma.1 packages instead of waiting. Red Hat’s CVE page scores it CVSS 9.8 but rates RHEL 9 and 10 Important, because those mod_http2 builds give each HTTP/2 stream its own memory allocator. The same page says public research has demonstrated a reliable exploit against a default-configured server with mod_http2 enabled, and that servers serving only HTTP/1.1 are not vulnerable. This guide carries no exploit code. The CVE wasn’t in CISA’s Known Exploited Vulnerabilities catalog (version 2026.11.10) when we looked, and we found no public exploit code. Neither of those is a reason to wait: treat any exposed host as urgent.
Check the version, module and Protocols line
Start with the package, not apache2 -v. Distros backport fixes without bumping the upstream number, so a patched Ubuntu build will still print 2.4.66 and only the package revision tells you anything. On a fresh Ubuntu 26.04 server, the package and module checks look like this:
sudo apache2 -v
apt-cache policy apache2
sudo apache2ctl -M 2>/dev/null | grep -i http2
cat /etc/apache2/mods-available/http2.conf
The empty -M result is the line that counts here. Ubuntu doesn’t load http2 by default, so this server isn’t exposed yet, but the last line shows what happens the moment anyone runs a2enmod http2:

Your production boxes may already have HTTP/2 on, usually enabled alongside TLS when the site went live. Our Apache setup guide for Ubuntu 26.04 leaves it off, so check whether you or a control panel added it later. To reproduce an exposed host, we ran a2enmod ssl http2, enabled default-ssl and added a small http2-protocols.conf with Protocols h2 h2c http/1.1, which is why that file shows up below. Debian keeps apache2 and apache2ctl in /usr/sbin, outside a normal user’s PATH, so run them with sudo on both distros. Grep the whole config tree for Protocols, then ask the server what it actually speaks, because a config file can be shadowed by another one:
sudo apache2ctl -M 2>/dev/null | grep -i http2
sudo grep -rn "^\s*Protocols" /etc/apache2/
curl -sk --http2 -o /dev/null -w "%{http_version}\n" https://localhost/
curl -s --http2 -o /dev/null -w "%{http_version}\n" http://localhost/
curl -s --http2-prior-knowledge -o /dev/null -w "%{http_version}\n" http://localhost/
This Debian 13 server answers 2 on all three probes: HTTP/2 over TLS, the h2c upgrade on plain port 80, and h2c with prior knowledge. The second and third results are the part people miss. Even a site that only serves HTTPS to browsers is reachable over cleartext h2c on port 80 if h2c sits in the Protocols line:

On Rocky Linux and AlmaLinux, mod_http2 is its own package, separate from httpd, and that’s the package the fix touches. Query both, then check the module and the Protocols line the same way:
rpm -q httpd mod_http2
httpd -M 2>/dev/null | grep -i http2
cat /etc/httpd/conf.modules.d/10-h2.conf
sudo grep -rn "^\s*Protocols" /etc/httpd/
We pinned the older 2.0.29-3.el10 build on this Rocky Linux 10 box to reproduce an unpatched host. It loads http2_module from 10-h2.conf, yet the grep for Protocols comes back empty.

With no Protocols line, httpd falls back to HTTP/1.1, and our curl probes returned 1.1 over TLS and 0 for h2c prior knowledge, which is curl’s way of saying no HTTP response came back. After we dropped Protocols h2 h2c http/1.1 into /etc/httpd/conf.d/http2-protocols.conf and restarted, the same probes returned 2 three times. So a Rocky or Alma server is exposed only if someone on your team added that line, which is common on anything fronting a modern browser audience. Check every file under conf.d, including vhost files a control panel wrote. DirectAdmin is the exception: it builds its own Apache through CustomBuild and keeps HTTP/2 always on, so dnf never patches it, and our DirectAdmin CustomBuild Apache patch guide walks through that rebuild.
Patch AlmaLinux 9 and 10 with dnf
AlmaLinux shipped patched mod_http2 builds on 11 November without publishing an ALSA advisory. That breaks the command you’d probably reach for first. dnf upgrade --cve CVE-2026-119618 filters on advisory metadata, finds none, and reports nothing to do while the fix sits in AppStream:
sudo dnf check-update mod_http2 httpd
sudo dnf upgrade -y --cve CVE-2026-119618
This AlmaLinux 10 box was pinned to the older 2.0.29-3.el10 build to stand in for an unpatched server (a fresh install already gets the fix). The first command lists the .alma.1 build, and the second shrugs.
mod_http2.x86_64 2.0.29-4.el10_2.2.alma.1 appstream
Last metadata expiration check: 0:00:55 ago on Thu 12 Nov 2026 04:28:36 AM UTC.
No security updates needed, but 10 updates available
Dependencies resolved.
Nothing to do.
Complete!
Upgrade the package by name instead. The transaction touches only mod_http2, so httpd keeps running its existing build and the restart is the only disruption:
sudo dnf upgrade -y mod_http2
rpm -q httpd mod_http2
rpm -q --changelog mod_http2 | head -3
sudo systemctl restart httpd
The changelog is your proof, because it names the CVE directly: the top entry, dated 11 November, reads mod_http2: heap corruption and RCE in assign_headers (CVE-2026-119618). Notice that httpd stays at 2.4.63-13.el10_2.8 through the whole run.

AlmaLinux 9 behaved the same way: mod_http2 moved from 2.0.26-5.el9 to 2.0.26-6.el9_8.2.alma.1 and httpd stayed at 2.4.62-13.el9_8.9. On both releases our curl probes still returned 2 after the restart, so the patched module keeps serving HTTP/2 and you don’t need a workaround once it’s installed. If you automate patching with the --cve or --security filters, as we do for PHP2Shell on RHEL, Rocky and AlmaLinux, add an explicit mod_http2 upgrade to this week’s run.
Patch RHEL 9 and 10 from the RHSA
Red Hat fixed it in two advisories dated 11 November, and both change only the mod_http2 package. RHSA-2026:98981 ships mod_http2-2.0.26-7.el9_9.1 for RHEL 9 and RHSA-2026:98978 ships mod_http2-2.0.29-5.el10_3.1 for RHEL 10. Both also fix CVE-2026-57941, a mod_http2 use-after-free. Because the advisories exist in Red Hat’s update metadata, the CVE filter should find them on a subscribed host:
sudo dnf upgrade --cve CVE-2026-119618
rpm -q mod_http2
sudo systemctl restart httpd
We didn’t run this on a subscribed RHEL box. Rocky and Alma stood in for RHEL in the lab. Treat rpm -q as your real check and compare it with the NVR above. If the filter returns nothing, sudo dnf upgrade mod_http2 gets the same package. Note the minor-release tags too: el9_9 and el10_3 builds come from the 9.9 and 10.3 streams, so a host pinned to an older minor release through releasever or an EUS repo won’t see them until Red Hat ships a fix for that stream. The full dnf checks and fixes for all three distros are in our RHEL, Rocky Linux and AlmaLinux patch guide.
Hold Rocky Linux until the rebuild lands
Rocky had no fixed build on 12 November, and a second Rocky 10 check that evening still found no new mod_http2 in AppStream. The newest mod_http2 in its AppStream is 2.0.29-4.el10_2.2 on Rocky 10 and 2.0.26-6.el9_8.2 on Rocky 9, the same versions Alma patched, and neither changelog mentions the CVE. Don’t take an available update as the fix. On the pinned Rocky 10 box, an update shows up but no advisory does:
sudo dnf check-update mod_http2 httpd
sudo dnf updateinfo list --cve CVE-2026-119618
The advisory query prints only its metadata line, which means no RLSA covers this CVE yet.
mod_http2.x86_64 2.0.29-4.el10_2.2 appstream
Last metadata expiration check: 0:01:18 ago on Thu 12 Nov 2026 04:22:06 AM UTC.
Install that update anyway, since it fixes older CVEs. Then read the changelog of what you just installed:
sudo dnf upgrade -y mod_http2
rpm -q httpd mod_http2
rpm -q --changelog mod_http2 | head -2
httpd is untouched and the newest changelog entry is from June, months before this CVE was reported:

Rocky 9 gave the same result: dnf changed only mod_http2, and its changelog doesn’t name CVE-2026-119618 either. You’re still exposed after the upgrade, so use the Protocols workaround below until a changelog entry naming CVE-2026-119618 arrives. Re-run the rpm -q --changelog check daily, because a Rocky build without an RLSA would slip past the --cve filter exactly the way Alma’s did.
Rocky 8 and every other EL8 rebuild can stop here. Red Hat says mod_http2 versions before 2.0.8 don’t contain the affected code, and the Rocky 8.10 box we checked runs the old module stream:
httpd -v
rpm -q httpd mod_http2
Apache 2.4.37 with mod_http2 1.15.7 is well outside the affected range, so you have nothing to patch for this CVE.

For Rocky 9 and 10, the workaround is to take h2 and h2c out of every Protocols line, server-wide and in each vhost, or delete the file that adds them. Our Rocky test above shows that a config with no Protocols line serves only HTTP/1.1, even with http2_module loaded. Restart httpd and re-run the three curl probes to confirm.
Patch Debian 13 and 12 with apt
Debian moved fast. DSA-6620-1, sent on 12 November, ships apache2 2.4.71-1~deb13u1 to trixie-security and fixes CVE-2026-119618 together with the two other 2.4.71 bugs covered further down. Debian takes the whole upstream release rather than a backport here, so the version number really does move to 2.4.71. The Debian 13 and 12 patch guide tracks the advisory and tracker status for both releases. Upgrade the package and read its changelog:
sudo apt-get update
sudo apt-get install -y --only-upgrade apache2
apt-cache policy apache2
zgrep -m3 -n CVE-2026-119618 /usr/share/doc/apache2/changelog.Debian.gz
sudo systemctl restart apache2
Our fresh Debian 13 box already pulled the fixed build at install time, so --only-upgrade had nothing left to do. Line 4 of the changelog closes all three CVEs, and the curl probes still return 2 after the restart. HTTP/2 stays on once you’re patched:

Debian 12 is the odd one. bookworm-security already serves apache2 2.4.71-1~deb12u1, and its changelog names CVE-2026-119618, yet there’s no DSA or DLA for bookworm and the Debian security tracker still listed bookworm as vulnerable when we checked on the evening of 12 November. The same apt commands work there, and the package is what counts:

That bookworm build is a bigger jump than the trixie one. It goes straight from 2.4.68 to 2.4.71 and closes 23 CVEs in one go, so test it on a staging host first if your vhosts lean on unusual modules. Vulnerability scanners that read the tracker may keep flagging Debian 12 hosts until the advisory appears. The changelog line is your evidence that the fix is in. The full apt walkthrough for both releases is in our guide to patch Apache on Debian 13 and 12.
Turn off HTTP/2 on Ubuntu
Ubuntu is the gap. On 12 November its CVE page for CVE-2026-119618 still returned 404, the notice list had no apache2 entry, and the Ubuntu CVE tracker marked every release needs-triage at high priority. So Ubuntu 26.04, 24.04 and 22.04 all remain exposed wherever HTTP/2 is on. HTTP/2 is off after a plain apt install apache2 on all three, which means the hosts at risk are the ones where someone ran a2enmod http2. The same holds for any Debian host you can’t upgrade today.
Don’t skip 22.04 because its httpd says 2.4.52. That is below the upstream range, but the 2.4.52-1ubuntu4.23 security update swapped the bundled module for mod_http2 2.0.42, the last release inside the affected mod_h2 range of 2.0.8 to 2.0.42. On our 22.04 lab server, line 131 of the package changelog reads CVE-2026-48913.patch: update to version 2.0.42 of the http2 module, and you can find it on yours with zgrep -n "update to version 2.0.42" /usr/share/doc/apache2/changelog.Debian.gz. The 26.04 and 24.04 builds carry 2.0.42 as well. Our Ubuntu walkthrough for CVE-2026-119618 covers each release in more depth, including the prefork MPM quirk in the 22.04 http2.conf. Confirm the package on your own servers before you change anything:
apt list --upgradable 2>/dev/null | grep -i apache2
zgrep -c CVE-2026-119618 /usr/share/doc/apache2/changelog.Debian.gz
apt changelog apache2 2>/dev/null | head -5
Both Ubuntu lab servers gave the same answer: no apache2 upgrade and zero changelog hits. On Ubuntu 26.04 the newest entry is an unrelated denial of service fix:

The cleanest workaround is to unload the module. Browsers fall back to HTTP/1.1 over the same TLS connection, so nothing breaks for visitors; you lose multiplexing, which costs a little latency on asset-heavy pages and nothing else. Our guide to disable HTTP/2 in Apache without patching also covers the Rocky Linux steps and the proxy_http2 dependency error. Disable it, test the config and restart:
sudo a2dismod http2
sudo apache2ctl configtest
sudo systemctl restart apache2
Then repeat the curl probes from the check section. The TLS and upgrade probes drop to 1.1 and prior knowledge fails with 0, which is what you want:

If something on the box needs mod_http2 loaded, set the protocol per virtual host instead, and this is where our first attempt went wrong. We wrote Protocols http/1.1 into a server-wide conf on Debian 13, restarted, and curl still negotiated 2 on all three probes, with mods-enabled/http2.conf still saying h2 h2c. httpd adds each Protocols line in the same scope to one list rather than replacing it, so the server list still held h2 and h2c. A vhost uses its own list once it has any Protocols line, and falls back to the server list only when it has none.
That gives you two cases. Where a vhost already has a Protocols line (the grep from the check section shows it), edit that line down to Protocols http/1.1, because appending a second one leaves h2 in the list. Where a vhost has none, as Debian’s two default sites don’t, add one before the closing tag. Run the sed once only, since a second run adds a duplicate line:
sudo sed -i '/<\/VirtualHost>/i \\tProtocols http/1.1' /etc/apache2/sites-available/000-default.conf /etc/apache2/sites-available/default-ssl.conf
sudo grep -rn "^\s*Protocols" /etc/apache2/
sudo systemctl restart apache2
sudo apache2ctl -M 2>/dev/null | grep -i http2
curl -sk --http2 -o /dev/null -w "%{http_version}\n" https://localhost/
curl -s --http2 -o /dev/null -w "%{http_version}\n" http://localhost/
curl -s --http2-prior-knowledge -o /dev/null -w "%{http_version}\n" http://localhost/
With the module still loaded, you should see HTTP/1.1 on both TLS and the upgrade probe, and no answer to prior knowledge.

Swap in your own vhost file names; the two above are Debian’s defaults. A vhost you miss keeps inheriting h2 h2c, so check every name-based site with curl using its real hostname, not only localhost. A CDN or load balancer in front of Apache may only speak HTTP/1.1 to the origin. Any client that reaches port 80 or 443 directly can still negotiate h2c or h2, though, so you still need the workaround.
Check the two other CVEs fixed in 2.4.71
Apache 2.4.71 closed two more bugs alongside the mod_http2 one, and Debian’s DSA-6620-1 carries all three in a single apache2 build. Apache rates neither as remote code execution, and each one lives in a module most servers never load:
| CVE | Apache rating | Module | Affected upstream | Effect |
|---|---|---|---|---|
| CVE-2026-106023 | Important | mod_md | 2.4.30 to 2.4.70 | NULL pointer dereference crashes a child process |
| CVE-2026-109163 | Low | mod_vhost_alias | 2.4.69 and 2.4.70 | 1-byte stack buffer overwrite |
mod_md is Apache’s built-in ACME client, so CVE-2026-106023 only matters if you get certificates through MDomain directives rather than certbot. The mod_vhost_alias bug hits only the two newest upstream releases, which among the packages in our table means an unpatched Debian 13 on 2.4.69. Run the -M listing from the check section again and look for md_module or vhost_alias_module. If neither shows up, these two don’t touch you. The Red Hat advisories above list only the mod_http2 CVEs, and Ubuntu had no notice for any of the three on 12 November.
Switch HTTP/2 back on after patching
The workaround is temporary. Once the fixed package lands, reverse it: sudo a2enmod http2 on Debian and Ubuntu, or remove the per-vhost lines, then restart and confirm curl returns 2 again. The patched Alma and Debian builds kept serving HTTP/2 in our tests, so there’s no reason to leave it off. The order we’d follow on a mixed fleet:
- RHEL and AlmaLinux: upgrade mod_http2 today, by name on Alma
- Debian 13 and 12: upgrade apache2 to the 2.4.71 build today
- Rocky 9 and 10, Ubuntu 26.04, 24.04 and 22.04: remove h2 and h2c now
- EL8: nothing to do for this CVE
- Every unpatched host: re-check the changelog daily, re-enable HTTP/2 once it names the CVE
On Ubuntu, watch for apache2 through your regular update channel, the same way you’d pick up the APT CVE-2026-109518 fix. Patch Rocky the moment a changelog entry names CVE-2026-119618. If you run nginx as a front end to Apache, check the nginx alias heap overflow in the same maintenance window. The Linux kernel CVE-2026-98432 patch needs a reboot you can line up with the restart. Our verdict: if your mod_http2 is exposed and unpatched, don’t leave h2 on over the weekend. Turning it off costs a few milliseconds per page, while leaving it on risks the whole server.