Services

Start a project Chat on WhatsApp
News & Insights

Apache Fixed a Critical Web Server Flaw. Your WordPress Update Cannot Fix It

On 11 November 2026, Apache released version 2.4.71 to fix a critical flaw in the part of its web server that handles HTTP/2. The flaw is tracked as CVE-2026-119618, and Apache says it can lead to remote code execution. That means an attacker could run their own code on the server without logging in. If your website runs on an affected Apache server with HTTP/2 switched on, this is the update that matters this week. And it is not an update you can install from your WordPress dashboard.

What happened

The flaw sits in mod_http2, the Apache module that serves HTTP/2 requests. HTTP/2 lets a browser send many requests over one connection at the same time, and Apache handles them in parallel threads. A synchronisation fault in one function, assign_headers, can corrupt the memory of an Apache child process. Apache rates the flaw critical.

It affects Apache 2.4.55 through 2.4.70, but only on servers where HTTP/2 is switched on. Standalone mod_h2 releases 2.0.8 through 2.0.42 are affected too. A server that only serves HTTP/1.1 is not affected by this flaw, and a site that runs on LiteSpeed or nginx only is not affected either.

Apache credits two independent reports. Anthropic’s OSS Scanner reported the flaw on 26 October, and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research reported it on 3 November. Apache published the fix and its advisory on 11 November. The same release also fixes two smaller flaws, a crash in mod_md and a one byte overflow in mod_vhost_alias.

Red Hat scores the flaw 9.8 out of 10. CISA scored it 8.1 on 13 November. No attacks have been confirmed as of 15 November, and the flaw is not on CISA’s list of exploited vulnerabilities. But public test code posted on 12 November crashes affected servers, and Red Hat says public research has demonstrated a reliable exploit against a default configured server with HTTP/2 on. The window between disclosure and patching is exactly when a flaw like this is most dangerous, so treat the update as urgent.

Why your WordPress update cannot fix it

Apache sits in front of WordPress. It handles the connection before a request ever reaches PHP or WordPress. A plugin, a theme or a security plugin runs after Apache has handled the HTTP/2 connection, so none of them can patch it. Updating WordPress, plugins and themes is still good practice, but it changes nothing about the Apache build your site runs on.

Your WordPress dashboard cannot tell you which Apache build your host runs, or whether the fix is installed. The version number alone can mislead as well, because Linux distributions often keep an older Apache version number and backport the fix into it. The useful question is not which version the server reports, but whether the installed package carries the fix for CVE-2026-119618 and whether HTTP/2 is on.

This is the third server side flaw in a month that the WordPress layer could do nothing about on its own, after the PHP flaw and the Brotli library flaw. If you manage sites for clients, it helps to know in advance which host runs each one, which web server it uses, and who is responsible for patching it.

What it means for a small business

If your site runs on shared or managed hosting, your host controls the server, so the fix is theirs to install. Most small businesses never touch Apache directly. That does not make the flaw someone else’s problem. It makes one short message to your host your job.

If the flaw were used against your server, an attacker could run code with the web server’s privileges and reach the sites and data on that server. No customer data compromise has been reported through this flaw. The risk is the open window: the flaw is public, the fix is public, and test code is public. Every day an affected server stays unpatched, the chance grows that someone tries it.

Sites on LiteSpeed or nginx only are not affected by this particular flaw. Digilistan’s own website runs on LiteSpeed, so this flaw does not touch it. If you are not sure what your site runs on, that is one more reason to ask your host.

What to do about it

  1. Check your host’s status page or announcements for CVE-2026-119618 or Apache 2.4.71. Many hosts patch quietly within a day or two of a release like this. If you find a confirmation, you are done.
  2. If you cannot find one, send your host one message: does the Apache server for my site accept HTTP/2, and has the fix for CVE-2026-119618 been installed? Ask them to confirm that Apache was restarted after the update, because Apache keeps running the old module until it is restarted.
  3. If you run your own server, install Apache 2.4.71 or your operating system’s fixed package and restart Apache. The fixed build may carry a different version number, so follow your supplier’s advisory.
  4. If no fixed package is available yet, ask your server administrator to switch HTTP/2 off in Apache until the update is installed. Servers that serve only HTTP/1.1 are not affected, and visitors will still reach the site.
  5. Keep a current backup of your site files and database, stored off the server. A backup does not prevent a flaw like this, but it is what makes recovery possible if a server is ever compromised.
  6. Do not install a plugin or pay for a tool that promises to fix this. No WordPress product can patch Apache, and anyone selling one for this flaw is selling nothing.

The one message worth sending today

A critical server flaw with a public fix and public test code is a race between hosts patching and attackers trying. Your part of that race takes one message to your host. Send it today, and check the answer before the week is out.

If you would rather have someone else watch for updates like this and deal with your host, Digilistan’s Hosting and Setup service does that work for small businesses in the United Kingdom, the United States and Pakistan.

Related reading: PHP2Shell: The Critical Website Flaw Your WordPress Update Cannot Fix. WordPress Owners, Check Your Version Tonight: CISA Lists a Core Flaw as Exploited.

Sources: Apache HTTP Server 2.4 vulnerabilities. Wordfence: Critical Apache HTTP/2 Vulnerability: What WordPress Site Owners Should Know. WPinEU: Apache HTTP/2 CVE-2026-119618: What WordPress Sites Should Check.

Start the conversation

Tell us what you are building

Whether you need a website, a chatbot that never sleeps or a workflow that gives your team its evenings back, start with a short conversation. We reply to every serious enquiry personally.

  • Your message goes to the founder, not a call center.
  • We suggest the smallest service that fixes the problem.
  • The first conversation costs nothing but a few minutes.

Prefer to talk first? Message us on WhatsApp and skip the form.

Chat with us