CVE-2026-35397

jupyter-server path traversal allows access to sibling directories sharing root_dir name prefix

HIGH
8.8
CVSS Score
Published: May 5, 2026 at 07:37 PM UTC
Updated: August 28, 2026 at 04:32 PM UTC
3 products affected across 3 vendorsJupyter ServerOpenShift AIJupyter Server

Using jupyter_server by jupyter-server?

Get instant alerts when new vulnerabilities affect jupyter_server - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.6%
SSVC
PoC

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.18.0
Affected range stops below 2.18.0, so it looks safe — our inference, not a vendor statement
v < 2.18.0
Affected range stops below 2.18.0, so it looks safe — our inference, not a vendor statement
All versions
Vendor states this is fixed in 1787073546 (unaffected)
Vendor states this is fixed in 1787073593 (unaffected)
Vendor states this is fixed in 1787073605 (unaffected)
Vendor states this is fixed in 1787073713 (unaffected)
Vendor states this is fixed in 1787073717 (unaffected)
Vendor states this is fixed in 1787073913 (unaffected)
Vendor states this is fixed in 1787073929 (unaffected)
Vendor states this is fixed in 1787074078 (unaffected)
Vendor states this is fixed in 1787074331 (unaffected)
Vendor states this is fixed in 1787076481 (unaffected)
Vendor states this is fixed in 1787076778 (unaffected)
Vendor states this is fixed in 1787077779 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (6)

Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-35397
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2466858
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:43038
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:60520

SSVC — Action Prioritization

SSVCPoCNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-22

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card