Home / Insights / Article

Apache HTTP/2 Vulnerability CVE-2026-119618: Am I Affected?

Illustration of web servers connected to the cloud

CVE-2026-119618 is a critical Apache HTTP/2 vulnerability in mod_http2, the module that handles HTTP/2 traffic. It affects Apache 2.4.55 to 2.4.70 and is fixed in 2.4.71, released on 11 November 2026. Only servers with HTTP/2 switched on are exposed. If unsure, ask your host which Apache version you run and whether HTTP/2 is on.

This article covers what the flaw is, how to tell whether your server is exposed, which versions fix it, what to do if you cannot update straight away, and what to ask your web company or host.

What Is the Apache HTTP/2 Vulnerability?

It is a memory corruption bug in the mod_http2 module of Apache HTTP Server, a concurrency vulnerability that can let an attacker run their own code on the server. In security terms, that is remote code execution. The Apache security advisory describes it as heap corruption in the module's assign_headers() function, caused by a race condition, and rates it critical.

Red Hat's bulletin says no login is needed to attack it, only the ability to send HTTP/2 requests to the server. The Netherlands' national cyber security centre (NCSC-NL) scores it 9.8 out of 10 on CVSS v3, according to Censys. As at 12 November, the US National Vulnerability Database had not published its own score.

Apache credits two teams with finding it: Anthropic's OSS Scanner, which reported it on 26 October 2026, and Google Cloud Vulnerability Research, which reported it on 3 November.

Is Your Website Affected?

Your server is affected if it runs Apache 2.4.55 to 2.4.70 and has HTTP/2 enabled. According to Red Hat's security bulletin, three things must all be true:

  • the mod_http2 module is loaded

  • the Apache configuration lists h2 or h2c in a Protocols line

  • an attacker can reach the server over HTTP/2

Red Hat states that servers set up to serve HTTP/1.1 only are not vulnerable. So the version number alone does not settle it. A server on Apache 2.4.69 with HTTP/2 switched off is not exposed to this flaw, while the same version with HTTP/2 on is.

The standalone mod_h2 module, which some servers install separately, is affected from version 2.0.8 to 2.0.42.

Does This Affect WordPress Sites?

It can. Many WordPress sites run on Apache, but the flaw is in the web server, not in WordPress or its plugins. Updating WordPress and its plugins does not fix it. What matters is the Apache version on the server and whether HTTP/2 is turned on.

What If My Site Uses a CDN or Proxy?

A CDN or proxy in front of your server may be what your visitors connect to over HTTP/2, but that does not tell you how it talks to Apache behind it. None of the advisories says a proxy protects you. Check Apache itself: if HTTP/2 is off there, the flaw cannot be reached.

Which Versions Fix It?

Apache 2.4.71 fixes the flaw. Most servers get Apache from their Linux distribution, and Linux distributions publish their own patched packages. The Debian security tracker lists these fixed versions:

Debian releaseFixed apache2 packageAdvisory
Debian 13 (trixie)2.4.71-1~deb13u1DSA-6620-1
Debian 12 (bookworm)2.4.71-1~deb12u1DLA-4902-1

Red Hat says fixes are out for most affected products, including Red Hat Enterprise Linux 9 and 10, with the rest being expedited. On other systems, check your distribution's security notices for CVE-2026-119618.

How to Check Your Apache Version and HTTP/2

Ask your host first if you do not manage the server yourself. If you do, these checks tell you what you need to know.

Apache version: Apache is often called Apache httpd, after its program name. On Debian or Ubuntu, run apache2 -v. On Red Hat-based systems, run httpd -v.

Is mod_http2 loaded? Run apache2ctl -M | grep http2 on Debian or Ubuntu, or httpd -M | grep http2 on Red Hat. No output means the module is not loaded.

Is HTTP/2 being served? Red Hat suggests curl -kI --http2 https://localhost on the server itself. A reply starting "HTTP/2 200" means HTTP/2 is on. A reply starting "HTTP/1.1 200" means it is not.

A word on the version string: distributions sometimes patch a flaw without changing the upstream version number, so check the package version as well. On Debian, dpkg -s apache2-bin shows it.

Is the Apache HTTP/2 Vulnerability Being Exploited?

As at 12 November 2026, no attacks in the wild had been reported, according to Censys, and it had found no public proof-of-concept code. We could not find it in CISA's Known Exploited Vulnerabilities catalogue when we checked on 16 November.

That may change quickly. Censys counts around 1.5 million internet-facing hosts reporting an Apache version in the affected range, although it cannot tell how many of those have HTTP/2 switched on. A flaw this widely deployed, with a public fix to study, is the kind attackers work on.

What If You Can't Update Straight Away?

Turn HTTP/2 off until the update is in. Apache itself publishes no workaround, but Red Hat's interim step is to remove h2 and h2c from the Protocols line, leaving Protocols http/1.1, and restart Apache. Red Hat says this reduces the attack surface until the patch is installed. Once patched, you can turn HTTP/2 back on.

Switching off HTTP/2 support can make some pages load a little slower, but the site keeps working. It is a configuration change for your host or developer to make, not something to try on a live server without knowing the setup.

What to Ask Your Web Company or Host

If someone else runs your server, these questions get you a clear answer:

  • Which Apache version is serving my website, and which package version?

  • Is HTTP/2 enabled in Apache, and is mod_http2 loaded?

  • Has the server been updated to Apache 2.4.71 or the distribution's patched package?

  • If not yet, has HTTP/2 been switched off in the meantime?

A useful answer gives you version numbers and a yes or no on HTTP/2. "We're on top of security" without either is worth following up.

How This Affects Sites on Our Platform

We checked the builds our platform runs from on 16 November. They run Apache 2.4.69, but mod_http2 is not loaded and HTTP/2 is not enabled in Apache, so this flaw cannot be reached. We are moving them to the patched package as part of our normal updates.

That is the point of a managed platform: server-level patches like this are handled for you, alongside the website itself. Every plan includes backups and restoring from them at no extra cost. Our managed websites page sets out what each plan covers.

If your site is hosted elsewhere and ran an affected setup with HTTP/2 on, it is worth checking nothing changed while it was exposed. Our guide to signs your website has been hacked covers what to look for. For the earlier PHP flaw from October, see PHP2Shell: is your website affected?

CVE-2026-119618 FAQs

If you want hosting where server patches like this are handled for you, our managed websites plans set out what is included. Or get in touch and we can tell you whether your server is affected.

Which Apache versions are affected by CVE-2026-119618?

Apache HTTP Server 2.4.55 to 2.4.70 is affected, along with the standalone mod_h2 module from 2.0.8 to 2.0.42. Apache 2.4.71, released on 11 November 2026, fixes it. Servers are only exposed when HTTP/2 is enabled.

Is my server safe if HTTP/2 is turned off?

Yes, for this flaw. Red Hat states that servers serving HTTP/1.1 only are not vulnerable, because the bug is in the code that handles HTTP/2. You should still install the patched version, so the server stays safe if anyone turns HTTP/2 back on.

Does updating WordPress fix it?

No. The flaw is in Apache, the web server software, not in WordPress or its plugins. The fix is updating Apache on the server, which is a job for your host or whoever manages the server.

How serious is CVE-2026-119618?

Apache rates it critical, and NCSC-NL scores it 9.8 out of 10 (CVSS v3). An attacker who can reach a vulnerable server over HTTP/2 may be able to run code on it without logging in, which is remote code execution. As at 12 November 2026, no attacks had been reported.

Callum Robley

Founder & Lead Developer, Tea Powered Projects

Callum is a full-stack developer and the founder of Tea Powered Projects, a web design, development, and hosting company based in Nottingham, UK. With over 15 years of industry experience, he specialises in building reliable, scalable digital solutions for businesses of all sizes.

Published: 16th November, 2026Updated: 16th November, 2026

Ready to get started?

If you would like to find out more about our services, or if you would like us to work on your next project, contact us below!
★★★★★

5.0 rated on Google · 50+ projects delivered