A serious Apache bug could let attackers take over your website server

If your website runs on Apache, ask whoever looks after it to check this week. A serious bug fixed on November 11 lets someone with no password take over the server behind a site. The fix is version 2.4.71.

Apache is free software that serves up a huge number of websites. The bug only matters if a speed feature called HTTP/2 is switched on, and on a lot of servers it is.

What happened

On November 11, 2026, the Apache project released version 2.4.71 of Apache HTTP Server. It fixes a flaw tracked as CVE-2026-119618 in the part of Apache that handles HTTP/2, the modern way browsers and web servers talk to each other. The Hacker News and security firm Bitsight both report that Anthropic's open source scanner reported the flaw to Apache on October 26. Apache rates it critical.

What this means in plain English

Think of a web server as a front desk that handles many visitors at once. This bug is a mix-up in how two staff members share the same notepad. If an attacker times things just right, the notepad gets scribbled over, and that can be turned into the ability to run commands on the machine. No username or password is needed. The attacker only has to reach the server over the internet.

Red Hat, a large Linux software company, says public research has shown a reliable attack against a server with the HTTP/2 feature turned on. Reports about whether attacks are already happening differ, so don't wait to find out.

Why a small business should care

A hijacked web server can mean a defaced or offline website, stolen customer or order details, or a foothold to reach other systems on your network. For a manufacturer or office that takes orders or quotes through its site, that means downtime and lost trust.

Who's affected

Apache HTTP Server versions 2.4.55 through 2.4.70, but only if HTTP/2 is turned on. Servers that only use the older HTTP/1.1 are not exposed. A separate add-on version of the HTTP/2 module (called mod_h2, versions 2.0.8 through 2.0.42) is affected too. Some Linux suppliers fix problems without changing the version number, so ask them as well. Red Hat says its older RHEL 8 and earlier are not affected.

What to do: everyone

  1. Find out who looks after your website. This may be an IT provider, a web design company or a hosting company.

  2. Ask them in writing: "Do we run Apache, and which version?"

  3. Ask whether HTTP/2 is turned on for our site.

  4. If we are on 2.4.55 to 2.4.70, ask them to update to 2.4.71 or a fix confirmed by the Linux supplier, and tell you when it's done.

  5. If the update can't happen this week, ask them to turn HTTP/2 off for now. Both Bitsight and The Hacker News describe this as a temporary stopgap, not a fix.

What to do: if you run the business

Make sure one named person is responsible for your website server and that it's on a regular update schedule. Ask for a short list of every public-facing system you have: website, email gateway, remote access. Servers that run quietly for years are the ones that get missed.

Questions to ask your IT provider

  • Which version of Apache are we running, and is HTTP/2 enabled on it?

  • When will we be on 2.4.71 or a supplier-confirmed fix?

  • Can you check the server for crashes or odd activity since before the update?

  • What else faces the internet that we don't update on a schedule?

Sources

Contact Nautalex to see how we can help you with keeping your website server updated.

Previous
Previous

Microsoft, US air traffic control and Apple all went down in six days. None of it was hackers.

Next
Next

Java has a serious new security hole. Is it hiding in your business software?