Skip to main content
Security

Apache rates its HTTP/2 flaw critical, and the fix is with whoever runs your server

Apache HTTP Server 2.4.71 fixes a critical flaw that can lead to remote code execution on servers with HTTP/2 switched on. Versions 2.4.55 to 2.4.70 are affected. How to check, and what to ask your host.

By Published Updated
A cartoon robot slides a new server unit into a rack topped with a security warning shield

Updated, 19 November 2026, 17:35 GMT. Singapore’s Cyber Security Agency said in an alert on 17 November that this flaw “is reportedly being actively exploited, and a proof-of-concept exploit is publicly available”. It doesn’t say who reported the attacks. The US Cybersecurity and Infrastructure Security Agency hadn’t added the flaw to its list of exploited vulnerabilities when we checked at 17:31 GMT on 19 November. If your host hasn’t confirmed the fix is in, ask them now.

Apache has fixed a critical flaw in its HTTP Server that can lead to remote code execution on servers with HTTP/2 switched on. If your host runs Apache, ask them whether the fix is in.

Apache HTTP Server is web server software that sits in front of many websites, including WordPress sites, and handles each connection before the site itself sees it. That makes this a fix for your host to apply, not something you can do from inside your website.

What Apache says

Apache’s security advisory rates CVE-2026-119618 critical. It describes a flaw in mod_http2, the module that handles HTTP/2 connections, that “can lead to RCE”, meaning remote code execution, which could let an attacker run code on the server. Apache HTTP Server versions 2.4.55 to 2.4.70 are affected, along with versions 2.0.8 to 2.0.42 of the separately released mod_h2 module.

Version 2.4.71, released on 11 November 2026, fixes it, along with two less serious flaws, one rated important and one low.

Who is exposed

Only servers that accept HTTP/2 through that module. Apache’s own default is the older HTTP/1.1, Wordfence says, but hosts can and do switch HTTP/2 on, so don’t assume yours is off. Wordfence also reports that Red Hat describes it as remote code execution without logging in when HTTP/2 is enabled.

Hosts and Linux distributions can patch Apache without changing its version number, so the version alone may not tell you whether a server is fixed, Wordfence notes.

Updating WordPress, your plugins or a security plugin won’t fix this. Those run after Apache has already handled the connection.

Is it being exploited?

Singapore’s Cyber Security Agency said on 17 November that the flaw “is reportedly being actively exploited, and a proof-of-concept exploit is publicly available”. It told users to update “immediately”. Its alert doesn’t name the source of the reports or say who has been attacked, and doesn’t say whether the public exploit runs code on the server or only crashes it.

Before that, cloud security company Wiz said on 11 November it wasn’t aware of any public exploits or attacks, BleepingComputer and Wordfence reported. The US Cybersecurity and Infrastructure Security Agency hadn’t added it to its catalogue of exploited vulnerabilities when we checked on 19 November.

How to tell whether your site uses HTTP/2

You can see which protocol your site’s visitors get. In Chrome or Edge, open your site, press F12, go to the Network tab and reload the page. Right-click the column headings, tick Protocol, and look at the row for your page: “h2” means HTTP/2, “http/1.1” means HTTP/1.1, and “h3” means HTTP/3.

That shows what your visitors connect to, which isn’t always your host’s Apache server. If your site sits behind a content delivery network such as Cloudflare, you’ll see the network’s connection, and the server behind it may use something different. Seeing h2 doesn’t by itself mean your server runs Apache or an affected version either. Your host is the one who can say for certain.

What to ask your host

Something like this, sent to your host’s support or whoever runs your server:

Does the server my website runs on use Apache HTTP Server, and does it accept HTTP/2? If so, has the fix for CVE-2026-119618 been installed, either Apache 2.4.71 or a patched package from your Linux distribution? If not, when will it be, and will you switch HTTP/2 off until then?

Many hosts also post security updates on their status or announcements page, so check there first.

If you run your own server, update to Apache 2.4.71 or your distribution’s patched package, and restart Apache afterwards. Until you can, the security firm watchTowr’s advice, as reported by BleepingComputer, is to “patch now or drop h2 until you can”, meaning switch HTTP/2 off.

Still unknown

Whether it is actually being used in attacks and, if so, against whom, how many sites run an affected Apache version with HTTP/2 switched on, and which hosts have already patched.

Changes

Update, 19 November 2026, 17:35 GMT: Added Singapore’s Cyber Security Agency alert of 17 November saying the flaw is reportedly being actively exploited and that a proof-of-concept exploit is public, replaced the earlier paragraph on whether the flaw could be exploited, now that a proof-of-concept exploit is reported to be public, and updated what is still unknown.

Alex De Sousa is the founder of Digital Royalty, a software development company in Portsmouth that builds websites, web apps and AI tools for UK businesses.