CVE-2026-35397
jupyter-server path traversal allows access to sibling directories sharing root_dir name prefix
- State
- Published
- Severity
- 7.6 High
- Published
- May 5, 2026
- Updated
- Aug 28, 2026
- Reserved
- Apr 2, 2026
Description
Jupyter Server is the backend for Jupyter web applications. In versions 2.17.0 and earlier, a path traversal vulnerability in the REST API allows an authenticated user to escape the configured root_dir and access sibling directories whose names begin with the same prefix as the root_dir. For example, with a root_dir named "test", the API permits access to a sibling directory named "testtest" through a crafted request to the /api/contents endpoint using encoded path components. An attacker can read, write, and delete files in affected sibling directories. Multi-tenant deployments using predictable naming schemes are particularly at risk, as a user with a directory named "user1" could access directories for user10 through user19 and beyond. A user who can choose a single-character folder name could gain access to a significant number of sibling directories.
Version 2.18.0 contains a fix. As a workaround, ensure folder names do not share a common prefix with any sibling directory.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 4.0 | 7.6 High | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N | GitHub_M |
| 3.1 | 7.1 High | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L | redhat-SADP |
Weaknesses
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Products
| Product | Versions |
|---|---|
jupyter_serverjupyter-server |
|
References
- https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-5789-5fc7-67v3
- https://access.redhat.com/security/cve/CVE-2026-35397vdb-entry
- RHBZ#2466858issue-tracking
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-35397.json
- https://access.redhat.com/errata/RHSA-2026:43038vendor-advisory
- https://access.redhat.com/errata/RHSA-2026:60520vendor-advisory
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.