↓Skip to main content
  1. News/

Apache Web Server Update: What to Ask Whoever Runs Your Website

On November 11, 2026, the Apache project released an update that fixes a serious flaw in Apache, free software that serves web pages for a large share of websites. The update has to be installed on the server by whoever runs it. So the useful question for an owner is “who updates our web server, and have they?”

What happened #

The Apache project rates the flaw “critical” and says the fix is in Apache 2.4.71, released on November 11. Its notice offers no workaround. Red Hat’s advisory says an outsider who can reach a vulnerable server could take control of it and run commands, with no login needed.

The flaw only matters where a feature called HTTP/2 is switched on. It is a faster way for visitors’ browsers to talk to a website, and many setups use it. Red Hat says servers set up to use only the older method are not affected. Whether it is on for your site is a setting that only the person who runs the server can check.

Security researchers reported the flaw to the Apache project before the fix came out. We found no source that names a business as attacked.

What this means for a website owner #

A website update will not fix it. SecurityWeek reported on November 12 that the WordPress security company Defiant warns WordPress updates cannot solve this, because the problem sits in the server underneath.

On shared hosting, the hosting company does the update. Your job is to ask, and to get a clear answer.

On a server your business or IT person runs, they have to install the update and then restart it. The old version keeps running until the restart.

Providers are moving at different speeds. The Hacker News reported on November 12 that some providers of server software had not yet released their own fixed versions. Their status pages changed through the day, so a host may still be waiting. Researchers at Wiz suggest that a server that cannot be updated yet can be limited to the older connection method for now. That removes one way in but does not fix the flaw, and it can slow a site down, so it is a decision for your IT person.

A version number alone proves nothing. That same report notes that providers give their own fixed versions their own numbers.

What we do not know #

Whether anyone is being attacked. The reports do not agree. Wiz said on November 11 that no attack code was available and that it had seen no reports of attacks. Red Hat says public research has shown a reliable attack on a standard setup, without saying whose. SecurityWeek says a public test program reportedly crashes servers but does not show control of one. As of November 12, none of the reports we read documented attacks in the real world. We cannot settle the rest.

How many websites are affected. The only figure we found is from Wiz: 51% of the cloud environments in its data have publicly reachable servers running an affected version. Wiz says that figure ignores settings, so it does not say how many have the faster connection method on.

Whether your own site is affected. That depends on the software version and on that one setting. Your host or IT person can tell you.

Five questions to ask this week #

  1. Does our website, and each booking or store page, run on Apache, and who is responsible for updating the server it runs on?
  2. Has the server been updated since November 11? Please answer in writing. A version number can mislead, and a written answer is clearer.
  3. Was Apache restarted after the update? The old version keeps running until it is.
  4. Is the faster connection method switched on for our site? If the update is not ready yet, can it be switched off until it is? This reduces exposure and does not fix the flaw.
  5. After the update, did anyone look for signs the server was already broken into? The reports we read list programs the web server should not start, files nobody recognizes, changed website files, and unusual connections going out from the server. An update closes the flaw. It does not tell you whether something got in first.

These questions will not prevent an attack. The update is the fix.

If you think a site was already broken into #

Call your host or IT person right away. The reports we read advise keeping the server’s logs and records, and changing the passwords and keys the web server could reach if there is evidence an attacker ran code.

Take this to your next IT meeting #

Send the five questions today and ask for written answers. If you are not sure who runs your website’s server, that is the first thing to find out.

At SOC-Lite, a named analyst reviews your alerts, calls you when one is real, works with your IT person or MSP on the fix, and keeps the evidence. A visibility check is free, it takes 20 minutes, and you talk to us by phone or at your office. Book a visibility check

Updates #

2026-11-12: First published, based on the sources below as of this date.

Sources #