Resources / Alert

Apache HTTP Server mod_http2 Flaw CVE-2026-119618: What to Check

Apache HTTP Server 2.4.71 fixes CVE-2026-119618, a critical flaw in the HTTP/2 module mod_http2. No attacks were known as of 19 November 2026. Which versions are affected, how to tell whether your site uses HTTP/2, and what to do.

On this page · 6 sections
  1. Short answer
  2. Is my site on Apache with HTTP/2?
  3. What to do
  4. What an outside check shows, and what it cannot
  5. Questions
  6. Sources

In 30 seconds

What happens
A flaw in mod_http2, the HTTP/2 module of Apache HTTP Server, can corrupt memory and may let an attacker run code; Apache fixed it in 2.4.71 on 11 November 2026.
Who it affects
Sites and servers on Apache HTTP Server 2.4.55 to 2.4.70 with HTTP/2 switched on, which can include shared hosting plans.
First step
Find out which Apache version your sites run and whether HTTP/2 is on, then update to 2.4.71 or ask your hosting provider to.
Our view
No attacks were known for this flaw when we checked, which is the best moment to deal with it: the fix exists and costs one update. The hard part is knowing which of your sites run on Apache and who updates them. We would start by asking every host and agency you use.

Facts checked on 19 November 2026.

On 11 November 2026, the Apache HTTP Server project released version 2.4.71. It fixes CVE-2026-119618, a flaw in mod_http2, the module that handles HTTP/2, a protocol every modern browser uses to load websites. Apache rates it critical: it can corrupt the server's memory and may lead to running code on the server. The CVSS 3.1 score listed on NVD, the US vulnerability database, added by CISA, is 8.1 out of 10. It is a different flaw from the NGINX HTTP/2 flaws we cover separately: it affects Apache HTTP Server only, and a fix and a low-cost stopgap both exist.

Short answer

  • Who is affected: Apache HTTP Server 2.4.55 to 2.4.70 with HTTP/2 in use. Apache also lists the separate mod_h2 module from GitHub, versions 2.0.8 through 2.0.42, as affected.
  • Is it attacked: no attacks were known as of 19 November 2026, and the flaw was not in CISA KEV, the US list of flaws with confirmed attacks (catalog of 18 November 2026). EPSS, a public estimate of how likely attacks are within 30 days, put it at about 1.6% on 18 November.
  • Is there a fix: yes, Apache HTTP Server 2.4.71, released on 11 November 2026.
  • What to do: update to 2.4.71, or ask your hosting provider whether they have. If you cannot update soon, stop offering HTTP/2 until you can.

Is my site on Apache with HTTP/2?

On your own server, two commands answer it:

apachectl -v                 # Apache version (on some systems: httpd -v)
apachectl -M | grep http2    # is mod_http2 loaded?

From any computer, this line shows whether a site speaks HTTP/2 (replace www.example.com with your site); the answer starts with "HTTP/2" if it does. The Server header may also name Apache and its version, but many servers hide it, and if a CDN sits in front, you see the CDN rather than your server:

curl -sI --http2 https://www.example.com | head -1

If your site is on shared hosting or a managed WordPress plan, send your provider one question: "Do our sites run on Apache HTTP Server 2.4.55 to 2.4.70 with HTTP/2, and have you installed 2.4.71?"

What to do

  1. Update to 2.4.71, or install the fixed package from your Linux distribution and compare it with the distribution's own advisory, since the version number may not change. Restart Apache.
  2. If you cannot update soon, stop offering HTTP/2. Remove h2 and h2c from every Protocols line, including those inside VirtualHost blocks (or set Protocols http/1.1 in each), and reload Apache. Apache's advisory lists no workaround; this is a common stopgap that keeps HTTP/2 traffic away from the affected module. Sites keep working over HTTP/1.1, though pages with many small files may load a little slower.
  3. Confirm. Check the version or the distribution package again; if you switched HTTP/2 off, the curl command above should answer "HTTP/1.1". Switch HTTP/2 back on once 2.4.71 is installed.

What an outside check shows, and what it cannot

An outside check shows what is reachable from the internet; it cannot see inside a server. Whether a server offers HTTP/2 is visible from the internet, because it is agreed in the first exchange between browser and server. The Apache version often shows too, unless it is hidden. What cannot be seen from outside is which module version is loaded, or whether a distribution has patched the server without changing the version number. So an outside check tells you which hosts to look at, not which ones are safe. Sites set up for old campaigns are the ones that get missed; it helps to compare what you think you expose with what is actually visible.

Questions

  • We run NGINX, not Apache. Then this flaw does not apply. NGINX has had HTTP/2 flaws of its own in November 2026; see our NGINX article.
  • Will switching HTTP/2 off slow our site? The site keeps working over HTTP/1.1. Pages with many small files may load a little slower; once 2.4.71 is installed, switch HTTP/2 back on.
  • How will we know if attacks start? CISA adds flaws with confirmed attacks to its KEV catalog. If this one is added, we update this article and the date at the top.

Sources

Get started

Know your risks before attackers find them.

Discover your external assets, identify security weaknesses and check for exposed corporate credentials with a free SeguriScan pilot. Get access to the platform, findings and reports to understand what needs attention.

  • Nothing to install
  • No access to your internal network
  • No active testing without your approval

We’ll contact you by email to discuss the pilot and agree on the next steps. No obligation to proceed. What’s included in the pilot →

By submitting this form, you acknowledge that IntruForce will process your personal data to respond to your request. See our Privacy Policy for details.