Notes · Christian Espiritu Kjeldsen
A critical Apache web server bug was fixed on Nov 11. Here's who has to do something.
On November 11, 2026, the Apache HTTP Server project released version 2.4.71 to fix a critical bug, CVE-2026-119618. Apache is one of the most common programs that serve websites. On a server running Apache 2.4.55 to 2.4.70 with HTTP/2 turned on, an attacker who needs no password could take over the web server. If your site is on Wix, Squarespace, Shopify or a similar builder, this is not yours to fix. If you pay for hosting, your host fixes it, and you should ask them one question. If you run your own server, update it today.
Checked November 12, 2026
The facts
Where does your website live?
Nothing for you to patch.
On a builder, the company runs the servers and patches them. You have no Apache settings to change. Keep your own login safe with two-step sign-in, and that's it for this one.
Your host patches it. Ask them, in writing.
Whether you're exposed depends on how the host set up the server. webhosting.today checked the big control panels: cPanel's default Apache setup leaves mod_http2 out, Plesk normally hands HTTP/2 to a different program (nginx), and DirectAdmin keeps HTTP/2 always on. So the honest answer is “ask”. Copy the short question below and send it to your host's support.
Update today, or turn HTTP/2 off.
Check the version with apachectl -v (or httpd -v). Look for h2 or h2c in the Protocols line of the main config and of every virtual host. Install 2.4.71 or your vendor's fixed package and restart Apache. If no package is out for your system yet, Wiz's stopgap is Protocols http/1.1, then a restart. Visitors will still reach the site; it just won't use HTTP/2.
Find out who you pay.
Look for a hosting or website charge on your card or bank statement, or ask whoever built the site. Once you know the company, pick the answer above that fits. If it's a builder, you're done.
The 4-box check
Tick what's already true. It builds a short to-do list you can copy. Nothing you tick leaves this page.
The question to send your host
Short and specific gets a faster answer. Paste it into a support ticket or chat.
What I'd do this week
- Sort out who owns the server. Most owners I talk to aren't sure. Ten minutes with a card statement fixes that for good.
- Send the question and keep the reply. A dated “yes, patched” from your host is all you need. If they say HTTP/2 isn't on for Apache, that's a fine answer too.
- If you run your own server, don't wait for an attack report. The patch is out. Updating and restarting Apache usually takes minutes.
What I can't tell you
I can't see how your host set up your server, so I can't tell you if you're exposed. Only they can. Some Linux systems had no fixed package yet when I checked; webhosting.today reported Debian's stable releases still listed as vulnerable on November 12. I'm not paid by any hosting or security company.
Sources
- Apache HTTP Server Project: Apache HTTP Server 2.4 vulnerabilities (fixed in 2.4.71, released Nov 11, 2026)
- Red Hat Customer Portal: CVE-2026-119618
- Wiz, Nov 11, 2026: Critical RCE vulnerability in Apache HTTP Server
- The Hacker News, Nov 2026: Critical Apache HTTP/2 flaw could let unauthenticated attackers execute code remotely
- SecurityWeek: Apache patches critical HTTP Server RCE found by Anthropic, Google
- Wordfence: Critical Apache HTTP/2 vulnerability, what WordPress site owners should know
- webhosting.today, Nov 12, 2026: On hosting servers, the panel setup decides who is exposed
Facts checked against the sources above on November 12, 2026.
Not sure what your website runs on?
Book a free 30-minute call. We'll look up where your site is hosted together, and I'll tell you plainly whether there's anything to do.
Book a free intro call