Apache CVE-2026-119618: Critical HTTP/2 Flaw (CVSS 9.8). Update to 2.4.71 or Turn Off HTTP/2

In short: CVE-2026-119618 is a critical (CVSS 9.8) bug in Apache’s mod_http2 that can let an unauthenticated attacker run code on the server. It affects Apache 2.4.55 to 2.4.70 with HTTP/2 enabled. Update to 2.4.71 (or your distro’s patched package), or turn HTTP/2 off until you can.
Last updated: November 14, 2026

Apache is still one of the most used web servers in the world, and plenty of Raspberry Pi home servers, WordPress sites and small VPSes run it. On November 11 the Apache project released 2.4.71 to fix a critical bug in its HTTP/2 support. If your server speaks HTTP/2, patch it now.

What the Bug Is

The flaw is a race condition in the assign_headers() function of mod_http2. When several HTTP/2 requests are handled at the same time, threads can touch shared memory without proper locking and corrupt the heap. Red Hat says a remote attacker without any login can use this to execute commands with the privileges of the web server process.

It was reported on October 26 by Anthropic’s OSS Scanner, an AI-based tool that audits open source code, and independently on November 3 by Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research.

Who Is Affected

SystemStatus (Nov 12)
Apache 2.4.55 – 2.4.70 with HTTP/2Vulnerable
Apache 2.4.71Fixed
Debian 13 (trixie)Fixed in apache2 2.4.71-1~deb13u1
Debian 12 (bookworm) / Raspberry Pi OS2.4.71 build in bookworm-security; check that apt installs it
Ubuntu 24.04 (2.4.58), 26.04 (2.4.66)Affected; watch for a USN update
Ubuntu 22.04 (2.4.52)Not in the affected range
RHEL 9 / 10Fixed in updated mod_http2 packages
Servers using only HTTP/1.1Not exposed

1. Check Your Version and HTTP/2

apachectl -v
apachectl -M | grep -i http2
grep -RniE '^\s*Protocols' /etc/apache2 /etc/httpd 2>/dev/null

Then test from another machine. If it prints 2, HTTP/2 is active:

curl -so /dev/null -w '%{http_version}\n' --http2 https://your-site.com/

2. Update Apache

# Debian, Ubuntu, Raspberry Pi OS
sudo apt update
sudo apt install --only-upgrade apache2
sudo systemctl restart apache2

# RHEL, Rocky, Alma
sudo dnf upgrade mod_http2 httpd
sudo systemctl restart httpd

Run apachectl -v again and check your distribution’s security tracker: some backport the fix without changing the version number to 2.4.71.

3. No Patch Yet? Turn HTTP/2 Off

If your distribution has not shipped a fix (Ubuntu, at the time of writing), disable HTTP/2. Your site keeps working over HTTP/1.1, just a little slower on pages with many small files.

# Debian / Ubuntu
sudo a2dismod http2
# and in every config or vhost with a Protocols line:
#   Protocols http/1.1
sudo apachectl configtest
sudo systemctl restart apache2

On RHEL-family systems, comment out the LoadModule http2_module line in /etc/httpd/conf.modules.d/10-h2.conf. Run the curl test again: it should now print 1.1. Turn HTTP/2 back on after you patch.

Also Fixed in 2.4.71

  • CVE-2026-106023 (important): a NULL pointer dereference in mod_md that crashes child processes (2.4.30 – 2.4.70).
  • CVE-2026-109163 (low): a one-byte stack overwrite in mod_vhost_alias (2.4.69 – 2.4.70).

Why It Matters

Web servers are the front door of everything you self-host. This is the second critical open-source server bug in a few weeks after PHP2Shell, which attackers are now using against Check Point gateways. Patch quickly, expose as little as possible and check which ports are open on your server. Running a Pi as a web server? Our Raspberry Pi home server guide covers the basics.

Frequently Asked Questions

What is CVE-2026-119618?

A critical race condition in mod_http2, the Apache HTTP Server module that handles HTTP/2. Concurrent HTTP/2 requests can corrupt heap memory, and an unauthenticated attacker may be able to run code on the server. Red Hat scores it 9.8.

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. It only matters if HTTP/2 is enabled. Version 2.4.71 fixes it.

Is my server vulnerable if I only use HTTP/1.1?

No. The bug is only reachable when Apache negotiates HTTP/2 (h2 or h2c) through the Protocols directive. Apache’s default is HTTP/1.1, but many distributions, control panels and tutorials turn HTTP/2 on.

Is it being exploited?

As of November 12, Wiz and others reported no confirmed exploitation and the CVE is not in CISA’s Known Exploited Vulnerabilities list, while Red Hat says public research has shown a reliable exploit against default configurations. Treat it as urgent.

What about Nginx or Caddy?

They are not affected: this bug is in Apache’s own HTTP/2 module.

Sources

Leave a Comment