How to protect your Apache server from CVE-2026-119618 and CVE-2026-57941 (mod_http2)

What is CVE-2026-119618?

CVE-2026-119618 is a race condition in mod_http2, the module that provides HTTP/2 support in Apache HTTP Server. It corrupts heap memory and, according to Apache, can lead to remote code execution (RCE). Apache rates it critical. It was published on November 11, 2026, together with the fixed release, Apache httpd 2.4.71.

Red Hat assigns it CVSS 3.1 9.8: exploitable over the network, without authentication and without user interaction (for RHEL 9 and 10 it lowers the rating to Important, because their packages make exploitation harder). As of November 12, 2026, there is no confirmed exploitation in the wild, and the vulnerability is not in the CISA KEV catalog. Red Hat states that public research has demonstrated a reliable exploit against a default-configured server with mod_http2 enabled: assume exploit code is already circulating or soon will be.

The October release: CVE-2026-57941

On October 1, 2026, Apache 2.4.69 fixed CVE-2026-57941, a use-after-free in the same module, mod_http2, affecting 2.4.17 through 2.4.68. Apache rates it moderate; according to Red Hat, the only demonstrated effect is a crash of the httpd worker, a denial of service (DoS).

  • Ubuntu fixed it (USN-8898-1): 2.4.52-1ubuntu4.24 on 22.04, 2.4.58-1ubuntu8.16 on 24.04 and 2.4.66-2ubuntu2.5 on 26.04.
  • Debian 13 fixed it with 2.4.69-1~deb13u1; the 2.4.71 packages for Debian 12 and 13 include it as well.
  • RHEL 9 and 10 fix it in the same packages as CVE-2026-119618. RHEL 8 remains unpatched.

Are you affected?

Only if your Apache has HTTP/2 turned on: according to Red Hat, HTTP/1.1-only servers are not affected, and by default Apache allows only http/1.1. If you never enabled it, you are probably not affected.

Your server is vulnerable to CVE-2026-119618 if all three conditions are true:

  • Apache httpd 2.4.55 through 2.4.70 without your distribution's patch, or the standalone mod_h2 module 2.0.8 through 2.0.42 (it has no fixed release).
  • mod_http2 is loaded.
  • A Protocols directive, global or inside a <VirtualHost>, includes h2 or h2c.

Depending on how Apache is packaged:

  • Debian and Ubuntu: a2enmod http2 turns on h2 and h2c at once. On a fresh Debian 12 install the module is not enabled.
  • RHEL, AlmaLinux and Rocky Linux: the package only loads the module; HTTP/2 is used only if you added a Protocols line. RHEL 8 and earlier are not affected by CVE-2026-119618, but they are affected by CVE-2026-57941.
  • cPanel with EasyApache 4: if ea-apache24-mod_http2 is installed (incompatible with the prefork and ITK MPMs), the server accepts h2 and h2c unless you changed it.

Fixed packages for CVE-2026-119618 as of November 12, 2026:

  • Debian 13: apache2 2.4.71-1~deb13u1 (DSA-6620-1)
  • Debian 12: apache2 2.4.71-1~deb12u1, in the security repository (its changelog lists the CVE, although the Debian tracker still marked it as vulnerable on November 12)
  • Ubuntu 22.04, 24.04 and 26.04: no fixed package
  • RHEL 9 / RHEL 10: mod_http2-2.0.26-7.el9_9.1 / mod_http2-2.0.29-5.el10_3.1
  • AlmaLinux 9 / AlmaLinux 10: mod_http2-2.0.26-6.el9_8.2.alma.1 / mod_http2-2.0.29-4.el10_2.2.alma.1
  • Rocky Linux 9 and 10: no fixed package
  • CloudLinux: no confirmed information; check the package changelog
  • cPanel EasyApache 4: ea-apache24 and ea-apache24-mod_http2 2.4.71-1.1.1.cpanel

Do not compare versions across distributions (the AlmaLinux builds compare lower than RHEL's and are fixed; Ubuntu backports the module): rely on the changelog of the installed package.

How to check your server

1. Is mod_http2 loaded? Run as root. On Debian and Ubuntu:

apache2ctl -M | grep -i http2
a2query -m http2

On RHEL, AlmaLinux, Rocky Linux and CloudLinux:

httpd -M | grep -i http2

A line reading http2_module (shared) means the module is loaded. If you get a configuration error, fix it: empty output caused by an error does not mean you are safe.

2. Which protocols are active? Look for Protocols directives:

grep -RniE '^[[:space:]]*Protocols' /etc/apache2 /etc/httpd 2>/dev/null

Ignore *-available directories, which are not active. Any active line with h2 or h2c enables HTTP/2. It does not cover configuration included from other paths.

3. Test from outside (from any machine with curl):

curl -V | grep -o HTTP2
curl -sI --http2 -o /dev/null -w '%{http_version}\n' https://YOUR_DOMAIN/

If the first line prints nothing, your curl lacks HTTP/2 support and the test is meaningless. A 2 confirms HTTP/2 is active. A 1.1 does not prove it is off: behind a CDN or reverse proxy you see the proxy, not your Apache, h2c on port 80 is not tested, and each virtual host is checked separately.

4. Do you have the patch? On Debian and Ubuntu:

apache2 -v
dpkg -l apache2 | tail -n 1
apt-cache policy apache2
zcat /usr/share/doc/apache2/changelog.Debian.gz | grep -n -m3 'CVE-2026-119618'

On Debian, if the last line finds the CVE, the patch is installed. On Ubuntu it will print nothing today: there is no patch yet.

On RHEL, AlmaLinux, Rocky Linux and CloudLinux (if the changelog names the CVE, the patch is installed):

rpm -q httpd mod_http2
rpm -q --changelog mod_http2 | grep -m3 'CVE-2026-119618'

On cPanel with EasyApache 4:

rpm -q ea-apache24 ea-apache24-mod_http2

2.4.71 or higher is fixed. If ea-apache24-mod_http2 is not installed, EasyApache is not providing mod_http2.

How to mitigate

All three options require an Apache restart.

Option Best for Durable?
A: install the fixed package Debian, RHEL 9 and 10, AlmaLinux 9 and 10, cPanel Yes
B: restrict Protocols to HTTP/1.1 No patch, if the Protocols line is yours (e.g., Rocky Linux) Temporary
C: disable mod_http2 No patch, especially Ubuntu, and RHEL 8 (CVE-2026-57941) Temporary

Option A: install the fixed package (recommended)

On Debian 12 and 13, the package restarts Apache when it upgrades, which briefly drops connections. That is why the command tests the configuration first; the final restart leaves the new version running:

sudo apt update
sudo apache2ctl configtest && sudo apt install --only-upgrade apache2 && sudo systemctl restart apache2

On Ubuntu this command does not fix CVE-2026-119618, because no package exists yet: use option B or C.

On RHEL 9 and 10 and AlmaLinux 9 and 10, upgrade only mod_http2, which is a separate package from httpd. The restart briefly drops connections:

sudo dnf upgrade mod_http2
sudo httpd -t && sudo systemctl restart httpd

On CloudLinux, confirm with the changelog after updating. On cPanel, update the EasyApache 4 packages through your usual procedure and confirm the version with rpm -q.

Option B: restrict Protocols to HTTP/1.1 (temporary workaround)

Apache has not published a workaround, but HTTP/1.1-only servers are not affected. If you cannot patch, replace every Protocols line that includes h2 or h2c with:

Protocols http/1.1

Check every <VirtualHost> too: its Protocols line overrides the global one. If the line comes from a packaged file (mods-available/http2.conf on Debian and Ubuntu, /etc/apache2/conf.d/http2.conf on cPanel), a package update can overwrite your change: there, option C is preferable on Debian and Ubuntu, and option A on cPanel. Test the configuration and restart Apache. Effect: clients fall back to HTTP/1.1.

Option C: disable mod_http2 (temporary workaround)

It leaves the server without HTTP/2, and the restart briefly drops connections. On Debian and Ubuntu, a2dismod removes both the module load and its http2.conf:

sudo a2dismod http2
sudo apache2ctl configtest && sudo systemctl restart apache2

On the RHEL family, this is the mitigation Red Hat published for CVE-2026-57941; it also removes the attack surface of CVE-2026-119618 and applies to RHEL 8. First edit /etc/httpd/conf.modules.d/10-h2.conf and comment out the module load line:

#LoadModule http2_module modules/mod_http2.so

Then test the configuration and restart; if you do it before saving the change, the restart has no effect:

sudo httpd -t && sudo systemctl restart httpd

After mitigating

  1. Confirm the patch with the changelog commands (zcat or rpm -q --changelog) or, on cPanel, with rpm -q.
  2. If you applied option B or C, repeat the curl test; it should return 1.1. It does not prove the module is unloaded or the package is patched.
  3. On Ubuntu and Rocky Linux, follow your distribution's tracker. When the fix ships, install it, restart Apache and revert the workaround (a2enmod http2 on Debian and Ubuntu, restore the LoadModule line on RHEL, or put your Protocols line back).
  4. As of November 12, 2026, no trusted source has published indicators of compromise (IoCs). Check the sources again: patch status is changing daily.

Need help?

Open a ticket at soporte.telecu.cloud and reference: CVE-2026-119618.

Sources

Tags
How to protect your OpenSSH server from sshole (CVE-2026-123158)