Jupyter Misconfiguration Exposes Systems to Root Privilege Escalation

Security researchers have identified a vulnerability in commonly misconfigured Jupyter notebook servers that can give attackers root-level access on Linux systems. The flaw stems from deployment choices rather than a Jupyter bug, with running a Jupyter server as root and without authentication creating a pathway to complete compromise. The attack uses Jupyter’s built-in terminal API, accessed via the unsecured /api/terminals endpoint and WebSocket connections, to open shell sessions without authentication.

In tests, commands such as id returned uid=0, confirming root access, and attackers can reach runtime configuration files stored in /root/.local/share/jupyter/runtime/ containing kernel ports, HMAC keys, and session information.

The researchers demonstrated a persistent backdoor by launching a reverse shell through the terminal, highlighting that this remains a deployment anti-pattern rather than an inherent Jupyter flaw. organisations should disable the terminal API when not needed, run Jupyter as an unprivileged user, implement strong authentication, and audit deployments immediately to remediate the dangerous configuration pattern.