Updated: 16 November 2026 · Applies to: CloudLinux OS with CageFS on cPanel and WHM

When CageFS is installed or updated on a cPanel server, every user whose shell is cPanel's jailed shell (jailshell) is switched to the normal /bin/bash in /etc/passwd. This is deliberate and safe: CageFS already gives each user their own isolated file system, and keeping jailshell on top of it would make cPanel's VirtFS create dozens of extra mounts for every user.

Why CloudLinux makes this change

cPanel's jailed shell works through VirtFS: when a jailed user logs in, cPanel builds a restricted view of the system under /home/virtfs/USERNAME with bind mounts. According to CloudLinux, when a user who is not in CageFS enters VirtFS, jailshell copies every mount point of the CageFS skeleton into that user's VirtFS tree, about 54 mounts per user. On a server with hundreds of accounts that adds up to a very large number of mounts, which slows the whole system down.

So the CageFS package replaces jailshell with bash. CloudLinux states that it is safe to give users an interactive shell such as /bin/bash when CageFS is enabled, and that CageFS is enabled for su, SSH and cron by default.

What users can still see

According to CloudLinux, inside CageFS only safe binaries are available, users cannot see other users or their usernames, cannot read server configuration files such as Apache's, and cannot see other users' processes in /proc. That is the same goal jailshell had, done in a way that does not depend on the shell.

Check that each bash user is really inside CageFS

The switch is only safe for users that CageFS covers. A user you excluded from CageFS gets plain bash with no isolation. Check this as root.

  1. See which mode CageFS runs in (all users enabled by default, or all disabled by default):
    /usr/sbin/cagefsctl --display-user-mode
  2. List the users who are excluded from CageFS:
    /usr/sbin/cagefsctl --list-disabled
  3. Check one user:
    /usr/sbin/cagefsctl --user-status alice
  4. If a user with shell access should be caged, enable CageFS for them:
    /usr/sbin/cagefsctl --enable alice

For anyone who should not have SSH at all, give them no shell instead of relying on jailshell. In WHM open Account Functions > Manage Shell Access and choose Disabled Shell.

Find users who still have jailshell

Accounts created after the CageFS update can still be given jailshell from WHM. This lists every user whose shell path contains jailshell:

awk -F: '$7 ~ /jailshell/ {print $1}' /etc/passwd

In a test on AlmaLinux 9.8 with one such account added, the output was:

carol

If CageFS covers those users, you can set them to Normal Shell in Manage Shell Access. If you leave them on jailshell, the VirtFS mounts described above build up again.

Related tasks

Official documentation: CloudLinux CageFS and CageFS PAM configuration.

Related services

KVM VPS hosting

NVMe SSD and full root access, with Free Basic Managed Support.

Unmanaged dedicated servers

full root access and free IPMI KVM, with Free Basic Managed Support.

Managed dedicated servers

our engineers look after the server for you, from $135 a month.

Was this answer helpful?

Still stuck? Open a ticket