Server CVE-2026-119618

Apache CVE-2026-119618

Apache HTTP Server 2.4.55 through 2.4.70 can run attacker code if HTTP/2 is on, CVE-2026-119618. The upstream fix is 2.4.71. A WordPress update does not patch Apache.

Also known as mod_http2, HTTP/2.

What happened

On Nov 11, 2026 Apache released HTTP Server 2.4.71 to fix CVE-2026-119618, a critical bug in mod_http2. That module is what Apache uses for HTTP/2. Apache lists 2.4.55 through 2.4.70 as affected, plus standalone mod_h2 releases 2.0.8 through 2.0.42. The bug is a race in assign_headers(): one thread can change a request's headers while another thread is still using them. Apache says that memory corruption can lead to remote code execution. Apache's default protocol is HTTP/1.1. HTTP/2 has to be turned on. A server that does not offer h2 or h2c through this module is not exposed to this bug.

Apache sits in front of WordPress. It accepts the connection before PHP runs, so the WordPress dashboard cannot tell you whether this module is patched. Tools, Site Health, Info, Server shows the PHP version. It does not show the Apache build or whether HTTP/2 is on. Updating WordPress, plugins, themes, or WP Security Ninja does not install the Apache fix. The Early Firewall runs in PHP after Apache has already accepted the HTTP/2 connection. See the Early Firewall guide.

Apache credits two reports: Anthropic's OSS Scanner on Oct 26, 2026, and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research on Nov 3. Apache rates the bug critical and does not publish a CVSS score. Red Hat scores it CVSS 3.1 9.8 and says public research has shown a reliable exploit against a default server with mod_http2 enabled. Red Hat does not link that research. On Red Hat Enterprise Linux 9 and 10, Red Hat rates the same bug Important rather than Critical, because those packages give each HTTP/2 stream its own memory allocator. Red Hat Enterprise Linux 8 and older do not contain the vulnerable code. Wiz, in a Nov 11 article, reported no known exploitation in the wild. We have not seen a report of a WordPress site broken into through this bug.

The version number on a host package is a weak signal. Ubuntu 22.04's apache2 package is 2.4.52, which sits below Apache's affected range, but CloudLinux says that package still carries mod_http2 2.0.42, which Apache lists as affected, and that Ubuntu had not shipped a fix as of Nov 12. CloudLinux says its own CloudLinux 7 and 8 system Apache is not affected, that CloudLinux 9 and 10 system mod_http2 packages are fixed, and that its EasyApache 4 rebuild for cPanel is on Apache 2.4.71. That rebuild is CloudLinux's, so a cPanel server that has not picked it up can still be on an affected build. Debian's security tracker lists DSA-6620-1 for trixie. After any update, Apache has to be restarted. The old module stays loaded until then.

Who is affected

WordPress sites whose Apache server accepts HTTP/2 (h2 or h2c) through the affected mod_http2. nginx, LiteSpeed, and OpenLiteSpeed use a different HTTP/2 stack. A CDN that speaks HTTP/2 to visitors does not, by itself, mean the Apache origin is exposed.

Fixed version: Apache HTTP Server 2.4.71. Host and Linux packages can use a different version number, so confirm the package changelog names CVE-2026-119618.

Do this now

  1. If the site is on nginx, LiteSpeed, or OpenLiteSpeed and Apache is not behind that proxy, this bug is not yours.
  2. On shared or managed hosting, ask the host this: does the Apache server for this site accept h2 or h2c, and does the installed package changelog name CVE-2026-119618? Ask them to confirm Apache was restarted after the update.
  3. Do not treat a WordPress, plugin, theme, or WP Security Ninja update as the fix.
  4. If you run the server, install Apache 2.4.71 or the vendor package whose changelog names CVE-2026-119618, then restart Apache. If that package is not out yet, turn HTTP/2 off. Remove h2 and h2c from the Protocols lines, including each virtual host, or disable mod_http2, then restart. Red Hat says a server that only speaks HTTP/1.1 is not affected.
  5. Check HTTP/2 on the Apache origin, not only on the public URL. A CDN or load balancer can speak HTTP/2 to browsers and still send HTTP/1.1 to Apache. Also check any direct or internal address that skips the CDN.
  6. Keep a current backup of the files and the database. A backup helps you restore a site. It does not block this bug.

Sources: Apache HTTP Server advisory Red Hat CloudLinux Wiz, Nov 11

You patched it. Now watch the site.

Pro adds a cloud firewall, malware scanning, and login protection. 14 days. Card or PayPal, not charged today.

Start 14-day Pro trial

Larger screenshot

Enlarged image