How to Check if Your Website's Server Needs the Apache HTTP/2 Fix
Apache fixed a critical HTTP/2 flaw on Nov. 11. Who is affected, the one question to ask your web host, and what to do if you run your own server.

Short answer: Apache, the free web server software that runs many websites, fixed a critical flaw in its HTTP/2 feature on Nov. 11. Only servers running Apache 2.4.55 through 2.4.70 with HTTP/2 switched on are affected. If a hosting company runs your site, ask it this week whether your server has the fix. If you run your own server, install Apache 2.4.71 or your Linux vendor's fixed package, or turn HTTP/2 off until you can.
Key points
The Apache HTTP Server Project rates CVE-2026-119618 critical and says it can lead to remote code execution. Version 2.4.71, released Nov. 11, fixes it.
Red Hat says an attacker would not need a password, and that servers serving only HTTP/1.1 are not vulnerable.
Cloud security firm Wiz wrote on Nov. 11 that it knew of no working exploit and no attacks. As of Nov. 13, the flaw is not on CISA's list of known exploited vulnerabilities.
Updating WordPress or its plugins won't fix this. The bug is in the server software underneath the site, as SecurityWeek reports security firm Defiant warned.
What to do this week: send your web host one short question (there's a copy-and-paste version below), and keep its answer with your website records.
What happened?
On Wednesday, Nov. 11, the Apache Software Foundation released Apache HTTP Server 2.4.71 with three security fixes. The most serious, CVE-2026-119618, is in mod_http2, the part of Apache that handles HTTP/2, a newer and faster way for browsers to load web pages. Apache's advisory describes it as a timing problem between threads that can corrupt the server's memory and "can lead to RCE," meaning an attacker could run their own commands on the server.
Apache credits two teams that found the bug on their own: Anthropic's OSS Scanner, which reported it on Oct. 26, and two researchers from Google Cloud Vulnerability Research, who reported it on Nov. 3. BleepingComputer and SecurityWeek both covered the two discoveries on Nov. 12.
Is my website affected?
Three things all have to be true, according to Apache and Red Hat:
Your site runs on Apache. Sites on other web server software, such as nginx or LiteSpeed, aren't running Apache's mod_http2.
The version is 2.4.55 through 2.4.70 and hasn't been patched by your hosting or Linux vendor. Vendors sometimes fix older version numbers in their own packages, so the number alone doesn't settle it.
HTTP/2 is turned on. Apache's own documentation says HTTP/2 has to be enabled with the server's Protocols setting before it's used. Red Hat's bulletin says a server with no "h2" or "h2c" in that setting is not vulnerable.
Wiz said on Nov. 11 that 64% of the cloud environments in its data had resources running affected Apache versions, and 51% had publicly exposed ones. Wiz and BleepingComputer both note that those figures don't account for whether HTTP/2 is actually on, and SecurityWeek points out they don't necessarily mean that many servers can be attacked.
How do I check if a host runs my site?
If you pay a hosting company, the server is its job, and you usually can't see its setup. Check its status page or announcements first. If you don't find a clear answer, send something like this:
"Does the Apache server that runs my website have HTTP/2 turned on, and has it been fixed for CVE-2026-119618 (the Apache 2.4.71 update from Nov. 11)? Please confirm Apache was restarted after the update."
A good answer names a patched version or package, gives a date, or tells you your site doesn't run on Apache.
On a WordPress site, you can take a first look yourself. WordPress's Site Health screen, under Tools > Site Health > Info, has a Server section that lists the web server software. It may not show a version number, and if your site sits behind a content delivery network, what visitors see may not be the server underneath, so your host's answer is still the one to rely on.
What if I run my own server?
Install Apache 2.4.71 or the fixed package from your operating system vendor, then restart Apache so the old code stops running. Red Hat, for example, says fixes are available for most of its affected products and that its older Enterprise Linux 8 and below aren't affected. Red Hat rates the flaw Important rather than Critical on 9 and 10 because of how those packages are built.
If you can't update yet, both Red Hat and Wiz advise removing "h2" and "h2c" from every Protocols line so it reads Protocols http/1.1, then restarting Apache. Red Hat says browsers fall back to HTTP/1.1 on their own, though pages may load a little slower until you turn HTTP/2 back on after patching.
Is anyone attacking this yet?
The sources don't fully agree, so here is what each says. Red Hat gives the flaw a severity score of 9.8 out of 10 and says public research has shown dependable exploitation of servers that have mod_http2 turned on, though SecurityWeek notes Red Hat didn't identify that research. Wiz said that when it published on Nov. 11, no exploit was available and it had no reports of attacks. SecurityWeek also reports that a public proof of concept on GitHub crashes Apache but doesn't show code execution.
As of CISA's Nov. 13 catalog update, CVE-2026-119618 was not listed as a known exploited vulnerability.
Our view: for a small business, this is a one-email task if a host runs your site, and a same-week update if you run your own server. Getting it closed before attack tools catch up is worth that effort.
Frequently asked questions
Will a WordPress or security plugin update protect me? No. The flaw is in Apache itself, which handles the connection before WordPress runs. SecurityWeek reports that security firm Defiant made the same point.
Will turning off HTTP/2 break my site? Red Hat says compatibility isn't affected because browsers switch to HTTP/1.1 automatically. The trade-off is somewhat slower page loads until HTTP/2 is turned back on after the fix.
Does this affect my office computers? Not directly. It affects web servers running Apache, not the browsers your staff use.
For more, see our guides to checking a WordPress site for an update flaw, patching a Linux server after a network flaw and locking down your business domain.
Disclosure: No company or organization named in this article paid for it, reviewed it or saw it before publication. Cybercave Technologies builds, hosts and manages websites for small businesses and offers remote IT support. Version numbers, dates and figures are as published by Apache, Red Hat, Wiz and CISA and were checked on Nov. 13, 2026. Not sponsored.
Sources
- PRIMARY: Apache HTTP Server Project, "Apache HTTP Server 2.4 vulnerabilities," entry for CVE-2026-119618 (fixed in 2.4.71, Nov. 11, 2026), checked Nov. 13, 2026
- PRIMARY: Apache HTTP Server documentation, "Apache Module mod_http2," checked Nov. 13, 2026
- PRIMARY: Red Hat Customer Portal, "CVE-2026-119618," checked Nov. 13, 2026
- PRIMARY: Red Hat, "RHSB-2026-017 Remote Code Execution - Apache HTTP Server (CVE-2026-119618)," Nov. 12, 2026
- PRIMARY: CISA, Known Exploited Vulnerabilities Catalog, version 2026.11.13, checked Nov. 13, 2026
- PRIMARY: WordPress.org Documentation, "Site Health screen," checked Nov. 13, 2026
- Wiz (Merav Bar), "Critical RCE Vulnerability in Apache HTTP Server: Everything You Need To Know," Nov. 11, 2026
- SecurityWeek (Eduard Kovacs), "Apache Patches Critical HTTP Server RCE Found by Anthropic, Google," Nov. 12, 2026
- BleepingComputer (Bill Toulas), "Apache HTTP Server patches critical HTTP/2 remote code execution flaw," Nov. 12, 2026
