A critical vulnerability in Apache, the web server used by many business websites, allows an attacker to take over the server without an account. A fix is available; contact your hosting provider.
The Apache Foundation has released version 2.4.71 of the Apache HTTP Server, which fixes CVE-2026-119618 (severity 9.8 according to Red Hat). The vulnerability is in the HTTP/2 module (mod_http2) and affects versions 2.4.55 through 2.4.70. An unauthenticated attacker can corrupt the server’s memory and execute code on it, meaning they could gain control of the website and the data on the server. The vulnerability was discovered independently by Anthropic’s open-source code scanner and by Google Cloud researchers.
This applies only to servers that have HTTP/2 enabled directly in Apache. The situation varies depending on the hosting control panel:
- cPanel/WHM: The default profile does not use the HTTP/2 module, so the server is only vulnerable if the administrator has enabled it; patched packages are now available for cPanel and CloudLinux.
- Plesk: HTTP/2 is enabled by default, but it typically passes through nginx, which is set up in front of Apache; it depends on how the server is configured.
- DirectAdmin: HTTP/2 can no longer be disabled from the control panel; vulnerability depends on which server handles HTTP/2 requests—Apache or another server running in front of it.
- Linux Distributions: Red Hat has patched RHEL 9 and 10 (RHEL 8 and earlier are not affected); for Debian stable and Amazon Linux, the fix was still in progress at the time the advisories were published.
No exploitation in real-world attacks (Wiz) has been reported yet, but Red Hat says that public research shows a reliable exploit on a server with default settings and HTTP/2 enabled. Web servers are automatically scanned as soon as such a vulnerability becomes known.
What you need to do:
- If your company's website is hosted by a hosting provider, ask them if the server is running Apache with HTTP/2 and if they have applied version 2.4.71 or the distribution's patched package.
- If you have your own server (VPS) or an IT provider managing it, request an update; until then, the temporary solution is to disable HTTP/2 in Apache (leaving only http/1.1 in the Protocols directive).
- Make sure you have a recent backup of the site, stored off the server.
Sources:
This article was generated with AI assistance.