LiteSpeed 6.3.7 Build 9 — CageFS Escape Fix: How to Update (November 2026)
Announced 11 November 2026. LiteSpeed Web Server 6.3.7 build 9 fixes a security flaw in how LiteSpeed reads Apache configuration. A website user could read files outside their own document root and run scripts without suEXEC, which on CloudLinux means getting out of CageFS, the wall that keeps each hosting account away from the others. On a shared server, one compromised site could then reach other customers' files. The update takes a couple of minutes and does not touch your sites' files or databases.
Already updated to build 8 for the HTTP/3 fix? You still need build 9: it is a separate fix. Builds are cumulative, so build 9 includes everything in build 8.
Am I affected?
Any server running LiteSpeed Web Server Enterprise 6.3.x older than 6.3.7 build 9 is affected. The risk is highest on shared hosting servers with CloudLinux and CageFS, where many customers share one server.
Check your version and build as root:
/usr/local/lsws/bin/lshttpd -v
cat /usr/local/lsws/BUILDYou are patched when the version is 6.3.7 and BUILD prints 9 (or higher).
Step 1 — Update LiteSpeed and refresh your licence
/usr/local/lsws/admin/misc/lsup.sh -f -v 6.3.7 ; tslzLSWSThe first command installs the newest build of 6.3.7 (build 9). The second refreshes your LiteSpeed licence so the server starts straight back up on the new build.
Step 2 — Verify
cat /usr/local/lsws/BUILD
/usr/local/lsws/bin/lshttpd -vBUILD must print 9 and the version must show 6.3.7. Then open a few of your sites to confirm they load normally.
What else is in build 9
- Bug fix: an endless loop that could happen in a rare case when LiteSpeed fetches a page internally.
- New setting
autoWhiteListLocalIps: controls whether the server's own local IP addresses are automatically trusted (whitelisted). You don't need to change anything for the update. - Stricter HTTP authentication: password-protected folders (HTTP Basic/Digest login) are checked more strictly. If a protected folder stops accepting a login that worked before, open a ticket and we'll help you adjust it.
Keep automatic stable updates on (optional)
Forcing a version with -f -v stops a plain lsup.sh run (for example from a cron job) from following LiteSpeed's stable channel. To turn stable-channel updates back on after this update:
touch /usr/local/lsws/autoupdate/follow_stableRelated advisories
- LiteSpeed 6.3.7 Build 8 — Critical HTTP/3 (LSQUIC) fix: covered by this update too.
- Critical cPanel WP Toolkit proxy flaw + PHP CVE-2026-115560: check this one if your server runs cPanel.
- All server security advisories
Managed-service customers
If your server is on one of our Server Management plans, we apply this update for you. Open a ticket if you'd like confirmation for your server. Not on a plan and would rather we did it? Open a ticket, share access, and we'll update LiteSpeed and check it for you.