Security

Apache HTTP/2 Vulnerability CVE-2026-119618: Update to 2.4.71 or Turn Off HTTP/2

A high-speed macro photograph of a blue drop and an orange drop of ink hitting the same glass of water at the same instant, their plumes colliding, a visual for the Apache HTTP/2 vulnerability, a race condition where two requests arrive together

An Apache HTTP/2 vulnerability, CVE-2026-119618, can let an attacker run code on a web server without logging in. The Apache HTTP Server Project rates it critical and fixed it in httpd 2.4.71 on November 11, 2026. It affects Apache 2.4.55 through 2.4.70 when HTTP/2 is turned on.

Apache serves a large share of WordPress and Drupal sites, on shared hosting, cPanel and Plesk servers, and self-managed VPSs. This post covers what the flaw is, who is exposed, which distribution packages fix it, and how to check a server. It also covers the stopgap if you cannot update yet, and what to ask your host. Facts are as of November 15, 2026.

The short version: fix the Apache HTTP/2 vulnerability by updating Apache, or the mod_http2 package on Red Hat systems, on every server you run. Debian, Ubuntu and Red Hat all ship fixes now. If you cannot update today, set Protocols http/1.1 and restart Apache. That turns HTTP/2 off, which removes the exposure. If a host runs your server, ask them in writing whether it is patched.

What the Apache HTTP/2 vulnerability is

Apache’s security vulnerabilities page for 2.4 lists the flaw as "mod_http2: heap corruption and RCE in assign_headers." RCE means remote code execution. Apache describes it as improper synchronization of a shared resource in the assign_headers() function, which "can lead to RCE."

In plain terms, the Apache HTTP/2 vulnerability is a race condition. Two threads touch the same memory at the same time, and one corrupts what the other is using. Red Hat’s CVE page explains that a worker thread writes into memory owned by the connection thread through a shared allocator. Red Hat says a remote attacker who can reach the server could run commands without authentication.

Red Hat scores it 9.8 out of 10 with CVSS 3.1. Its page also shows a score of 8.1 from cve.org, which rates attack complexity as high. Our guide to reading a CVSS score explains why the two numbers differ. If CVE numbers are new to you, start with what a CVE is.

Apache credits two finders. One is Anthropic’s OSS Scanner, which reported it on October 26. The other is Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research, who reported it on November 3.

Who is exposed to the Apache HTTP/2 vulnerability

Three things must be true for a server to be exposed:

  • The Apache version is in range. Apache lists 2.4.55 through 2.4.70.
  • HTTP/2 is on. Red Hat says only servers with HTTP/2 enabled are affected. Servers that speak only HTTP/1.1 are not.
  • The server is reachable. Anyone who can connect can try, per Red Hat.

The standalone mod_h2 module from GitHub is also affected, from 2.0.8 through 2.0.42, according to Apache. That GitHub repository was archived on June 9, 2026. Its README says the module now lives on inside the Apache httpd project. In practice, the fix is to move to a current Apache build.

Red Hat says RHEL 8 and earlier are not affected, because mod_http2 versions before 2.0.8 do not contain the affected code. Ubuntu lists 18.04 LTS and older as not affected.

Is the Apache HTTP/2 vulnerability being exploited?

The sources disagree on how close an attack is. Wiz wrote on November 11 that "no exploit is available and there are no reports of exploitation in the wild." Red Hat’s CVE page goes further on risk. It says "public research has demonstrated a reliable exploit against a default-configured server with the mod_http2 module enabled." Red Hat does not name or link that research.

As of November 15, Apache, Red Hat, Debian and Ubuntu do not report attacks in the wild on their pages. Treat that as no confirmed reports yet, which can change quickly with a flaw this serious. Wiz also reports that 64% of cloud environments it sees have resources with the vulnerable versions. Wiz notes that figure does not account for configuration, such as whether HTTP/2 is on.

Fixed packages by distribution

Most servers get Apache from the operating system, not from apache.org. Here is what each vendor ships for the Apache HTTP/2 vulnerability as of November 15.

System Fixed package Source
Apache source build httpd 2.4.71 Apache, November 11
Debian 13 (trixie) apache2 2.4.71-1~deb13u1 DSA-6620-1, November 12
Debian 12 (bookworm) apache2 2.4.71-1~deb12u1 DLA-4902-1 from Debian LTS
Ubuntu 26.04 LTS apache2 2.4.66-2ubuntu2.8 USN-9090-1, November 12
Ubuntu 24.04 LTS apache2 2.4.58-1ubuntu8.19 USN-9090-1
Ubuntu 22.04 LTS apache2 2.4.52-1ubuntu4.27 USN-9090-1
Ubuntu 20.04 LTS apache2 2.4.41-4ubuntu3.23+esm11 Ubuntu Pro only
RHEL 10 mod_http2-2.0.29-5.el10_3.1 RHSA-2026:98978, November 11
RHEL 9 mod_http2-2.0.26-7.el9_9.1 RHSA-2026:98981, November 11

The Debian versions come from Debian’s security tracker, which still lists Debian testing (forky) as vulnerable. The Ubuntu versions come from Ubuntu’s notice USN-9090-1, and Ubuntu’s CVE page rates the issue High. Red Hat’s fixes are in RHSA-2026:98981 for RHEL 9 and RHSA-2026:98978 for RHEL 10. Red Hat rates RHEL 9 and 10 Important, not Critical, because their mod_http2 builds give each HTTP/2 stream its own allocator. Red Hat says that makes the attack much harder.

Why the Apache version number can mislead you

Look at the Ubuntu rows. Ubuntu 24.04 is fixed in a package built on Apache 2.4.58, and 22.04 in one built on 2.4.52. Neither number is 2.4.71. Ubuntu’s CVE notes say newer HTTP/2 module code was backported to its stable releases. Debian and Red Hat backport fixes the same way.

So apache2 -v or httpd -v tells you the base version, not whether the fix is in. On distribution packages, check the full package version against the table instead. On a server built from source, or from a vendor’s own build, the Apache version is what counts. There, you need 2.4.71 or later.

How to check your server

These steps assume shell access. They come from Red Hat’s bulletin where noted. The rest is standard Apache administration.

  1. Find the package version. On Debian or Ubuntu, run dpkg -l apache2. On RHEL and its rebuilds, run rpm -q httpd mod_http2. Compare the result to the table.

  2. Check the Apache version on source builds. Run httpd -v or apache2 -v. Anything from 2.4.55 to 2.4.70 is in range.

  3. See whether the HTTP/2 module is loaded. On Debian or Ubuntu, apache2ctl -M | grep http2 lists it if loaded. On Red Hat, the bulletin suggests grep http2 /etc/httpd/conf.modules.d/*.conf.

  4. Look for h2 in the Protocols lines. Red Hat suggests grep -r 'Protocols' /etc/httpd/conf/ /etc/httpd/conf.d/. On Debian or Ubuntu, search /etc/apache2/ the same way. Any h2 or h2c means HTTP/2 is on.

  5. Test from the outside. Red Hat suggests curl -kI --http2 https://localhost. A first line of HTTP/2 200 means HTTP/2 is on. HTTP/1.1 200 OK means it is off.

HTTP/2 can be set server-wide or inside a single virtual host. Check every vhost file, not only the main config.

The workaround: turn off HTTP/2 until you can patch

Apache’s page lists no workaround for the Apache HTTP/2 vulnerability. Red Hat’s security bulletin RHSB-2026-017 gives one. Remove h2 and h2c from every Protocols directive, so the line reads Protocols http/1.1. Then restart Apache with systemctl restart httpd on Red Hat, or systemctl restart apache2 on Debian and Ubuntu. Wiz gives the same advice.

On Debian and Ubuntu you can also disable the module with a2dismod http2 and restart. That is standard Debian tooling, not a step from the advisories.

Red Hat notes the cost. Browsers fall back to HTTP/1.1, with some loss of speed and more bandwidth. Turn HTTP/2 back on after the update. Our post on HTTPS and TLS covers the TLS side, which this change does not touch.

Turning off HTTP/2 is a stopgap, not the fix. Install the patched package, confirm Apache restarted, then turn HTTP/2 back on.

What to ask your host, cPanel or Plesk provider

Many of our readers do not run their own servers. If a host or MSP manages yours, send them three questions:

  • Is the server on a fixed build for the Apache HTTP/2 vulnerability, CVE-2026-119618? Ask for the package version, not just "yes."
  • Is HTTP/2 on, and was the workaround applied while you patched?
  • When did Apache restart on the fixed build? A package update does not protect a process still running the old code.

cPanel servers get Apache through EasyApache 4. As of our check on November 15, cPanel’s public EasyApache 4 change log did not yet list an update for this CVE. Its newest Apache entry was the update to 2.4.69 on October 2. We found no Plesk notice on this CVE either. That does not mean those servers are safe. Ask your provider directly, and use the HTTP/2 workaround until they confirm.

Managed platforms often run their own web stack and patch it for you. Our guides to choosing a managed WordPress host and Pantheon versus Acquia cover what those plans include. Even so, ask.

WordPress and Drupal sites on Apache

The Apache HTTP/2 vulnerability sits in Apache itself, before PHP or your CMS sees the request. Keeping WordPress, Drupal, plugins and modules up to date does not cover it. Security plugins that run inside the CMS cannot see it either.

On shared hosting, one Apache install often serves many sites. A flaw in the web server puts every site on that box at risk, not only the one an attacker targets first. If you manage many client sites on one server, patch that server first.

A CDN or proxy in front of the site may connect to your server over HTTP/1.1. That helps only if the server refuses direct connections. If attackers can find the origin IP address, they can skip the CDN. Do not count on it in place of the patch.

If you suspect a server was hit before you patched, follow your data breach response plan. Our post on the PHP2Shell flaws covers checking a PHP web server after a code execution bug. For defense in depth, see our guide to blocking PHP execution in upload folders.

The other fixes in Apache 2.4.71

Apache 2.4.71 fixes three CVEs in total. The Apache HTTP Server home page calls the release "the best available version of Apache HTTP Server."

  • CVE-2026-106023, rated important. A NULL pointer dereference in mod_md crashes an Apache child process. It affects 2.4.30 through 2.4.70. The mod_md module handles automatic certificates from services like Let’s Encrypt. A crash means a denial of service, not code execution.
  • CVE-2026-109163, rated low. A one-byte stack buffer overwrite in mod_vhost_alias. It affects 2.4.69 and 2.4.70.

Ubuntu’s USN-9090-1 bundles these with two other Apache fixes, in mod_dav and in CGI handling. One standard update covers them all, Ubuntu says.

Frequently Asked Questions

What is the Apache HTTP/2 vulnerability CVE-2026-119618?

A race condition in Apache’s mod_http2 module. Apache rates it critical and says it can lead to remote code execution. Red Hat says no login is needed.

Which versions have the Apache HTTP/2 vulnerability?

Apache 2.4.55 through 2.4.70 with HTTP/2 turned on, plus standalone mod_h2 2.0.8 through 2.0.42. Apache 2.4.71 fixes it.

My server says Apache 2.4.58. Is it vulnerable?

It depends on the package. Ubuntu 24.04 ships the fix in apache2 2.4.58-1ubuntu8.19. Distributions backport fixes, so check the full package version, not only the Apache number.

Is the Apache HTTP/2 vulnerability being exploited?

Apache, Red Hat, Debian and Ubuntu do not report attacks in the wild as of November 15, 2026. Red Hat says public research has shown a reliable exploit, so patch now.

How do I know if HTTP/2 is on?

Search your Apache config for Protocols lines that include h2 or h2c. You can also run curl -kI –http2 against the site. A response that starts with HTTP/2 means it is on.

What is the workaround if I cannot update?

Set Protocols http/1.1 everywhere it appears, including virtual hosts, then restart Apache. That turns off HTTP/2, which the flaw needs.

Does turning off HTTP/2 break my site?

No. Browsers fall back to HTTP/1.1. Red Hat notes some loss of speed and more bandwidth use. Turn HTTP/2 back on after you patch.

Is RHEL 8 affected?

No. Red Hat says RHEL 8 and earlier do not contain the affected code. RHEL 9 and 10 are affected and have fixed mod_http2 packages.

Do WordPress or Drupal updates fix the Apache HTTP/2 vulnerability?

No. The flaw is in the Apache web server, not the CMS. Update the server package or ask your host to.

What else does Apache 2.4.71 fix?

A mod_md crash bug, CVE-2026-106023, rated important, and a low-rated mod_vhost_alias bug, CVE-2026-109163.

Digital Matters

Security Desk