TL;DR
On November 10, 2026, LiteSpeed fixed a vulnerability in LiteSpeed Web Server (LSWS) that let a hosting account’s script run without being placed in the account’s CageFS, the virtualized filesystem CloudLinux uses to isolate each hosting account. Hostinger’s incident report of November 9 describes the flaw being used on one of its shared servers.
LiteSpeed’s changelog lists the fix in LSWS 6.3.7 Build 9 and 6.4.0 RC2 Build 7. It describes the fix as hardening how LSWS handles Apache configuration, against file access beyond a site’s document root and "running scripts without suEXEC (CageFS escape)". It gives no CVE identifier.
CageFS contains the processes that run inside an account’s cage. Each one sees that account’s files and a limited set of system files, and nothing of the other accounts on the server.
LSWS runs outside CageFS. When a request reaches a site’s script, LSWS starts the script as the account’s own user and places it in the account’s cage. The vulnerability allowed a script to skip that step. It ran as the web server’s own user, outside any cage, so CageFS never applied to it.
On each server that runs LSWS:
Note that LiteSpeed’s September fix, in 6.3.7 Build 2, closed a different vulnerability (Hostinger’s September report describes it). A server updated at that time still needs Build 9.
Akos Vajda
Comments