Current status
| Step | Status |
|---|---|
| cPanel servers running Apache | ✓ Fixed version installed and HTTP/2 back on |
| Enhance servers running Apache | ✓ Fixed version installed and HTTP/2 back on |
| Servers running LiteSpeed | ✓ Not affected |
What is the issue?
Apache is web server software. It handles each visitor’s connection before the request reaches your website, whether that’s WordPress or anything else.
The flaw is in the part of Apache that handles HTTP/2, a newer, faster way for browsers to talk to web servers. By sending specially crafted HTTP/2 requests, an attacker could make the server run their own code, without needing to log in. That could put websites and data on the server at risk.
Apache only uses this part when HTTP/2 is switched on. A server that only accepts the older HTTP/1.1 is not exposed.
| Detail | Information |
|---|---|
| Reference | CVE-2026-119618 |
| Affected software | Apache HTTP Server, HTTP/2 module (mod_http2) |
| Affected versions | Apache 2.4.55 to 2.4.70, and standalone mod_h2 2.0.8 to 2.0.42 |
| Severity | Critical |
| Fixed in | Apache 2.4.71, released 11 November 2026 |
| Made public | 11 November 2026 |
Full details are in Apache’s security advisory.
What we have done
- 11/11/26: Apache published the flaw and released a fix.
- 12/11/26: we switched off HTTP/2 on all of our servers running Apache. This closed off the flaw straight away.
- 12/11/26: we installed the fixed version of Apache on all of our cPanel servers running Apache and switched HTTP/2 back on.
- 13/11/26: we installed the fixed version of Apache on all of our Enhance servers running Apache and switched HTTP/2 back on. This issue is now resolved.
Do I need to do anything?
No. If your website is hosted with us, this has already been taken care of.
Running your own server?
If you have a VPS or dedicated server that you manage yourself and it runs Apache with HTTP/2 switched on:
- Install the fixed version as soon as it’s available. Apache’s own fix is in version 2.4.71. If Apache came from your operating system or control panel (for example cPanel or CloudLinux), follow that supplier’s advisory. Its fixed package may carry a different version number.
- If no fix is available yet, switch off HTTP/2 in Apache. Remove
h2andh2cfrom theProtocolssetting in your Apache configuration, including any virtual hosts. - Restart Apache and check it no longer accepts HTTP/2.
- Switch HTTP/2 back on once the fixed version is installed.
CloudLinux has published checks and fixed builds for its hosting systems.
Was my website affected?
We are not aware of any websites on our platform being affected. When the flaw was made public, there were no known reports of it being used in real attacks, we switched off HTTP/2 the day after. The fixed version is now installed on all of our servers. If you have any concerns, we’re always happy to take a look.