Current status
| Server | Status |
|---|---|
| All PAC servers running LiteSpeed | ✓ Security fix installed |
What is the issue?
On shared hosting, lots of websites live on the same server. Each hosting account is kept in its own walled-off space, so one customer can never see or touch another customer’s files.
LiteSpeed found a problem in the way its web server handled certain settings. In some set-ups, it could have let someone with a hosting account read files outside their own website, or run scripts without the usual safety checks. On shared servers, the worst case was that they could break out of their own account’s walled-off space and take control of the whole server.
LiteSpeed rated the issue critical and released a fix on 10 November 2026.
| Detail | Information |
|---|---|
| Affected software | LiteSpeed Web Server (Enterprise) |
| Affected versions | All versions before the fixed versions below |
| Most at risk | Shared hosting servers that use Apache configuration with suEXEC and CloudLinux CageFS |
| Severity | Critical |
| Fixed in | LiteSpeed Web Server 6.3.7 build 9 (or 6.4.0 RC2 build 7) |
What we have done
- 10/11/26: LiteSpeed released the fix. We installed it on all of our servers running LiteSpeed and checked that everything is working normally.
Do I need to do anything?
No. If your website is hosted with us, this has already been taken care of.
As part of this update, LiteSpeed has also made its handling of password-protected folders (HTTP authentication) stricter. If you have a folder on your website that asks for a username and password before it opens, it should keep working as normal. If it doesn’t, please let us know and we’ll sort it out.
Running your own server?
If you have a VPS or dedicated server that you manage yourself and it runs LiteSpeed Web Server, update it now to:
- 6.3.7 build 9, or
- 6.4.0 RC2 build 7 if you’re on the 6.4 release candidate.
You can update from the LiteSpeed WebAdmin Console, or from the command line:
/usr/local/lsws/admin/misc/lsup.sh -f -v 6.3.7
Once updated:
- Check the new version is running.
- Check any password-protected folders still work as expected.
- On shared servers, look for signs of compromise, such as unfamiliar processes, files or cron jobs, or unexpected activity across accounts or as root.
If you think your server may have been compromised, change the server’s passwords, plus the database passwords and access tokens stored in its hosting accounts, as well as updating.
Was my website affected?
We are not aware of any websites on our platform being affected. To take advantage of this issue, someone would already need a hosting account on the same server, and we installed the fix on the day LiteSpeed released it. If you have any concerns, we’re always happy to take a look.