CVE-2026-35397: jupyter-server path traversal allows access to sibling directories sharing root_dir name prefix
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.
Security readout for executives and security teams
Plain-English summary
Authenticated users of Jupyter Server 2.17.0 or earlier can reach files outside their assigned root when nearby directory names share the same starting text. In multi-user environments, this can expose, modify, or delete another user's files. The vendor fix is 2.18.0; naming separation is a workaround.
Executive priority
Treat as high priority where Jupyter Server hosts multiple users or sensitive notebooks. The business risk is cross-user file exposure and tampering by an authenticated tenant. Upgrade promptly and review directory naming exposure.
Technical view
CVE-2026-35397 is a CWE-22 path traversal in Jupyter Server's contents API. A low-privileged authenticated user can escape the configured root_dir to sibling directories with matching prefixes. Reported impact includes read, write, and delete access in those sibling directories. CVSS v4.0 score is 7.6 high.
Likely exposure
Highest exposure is multi-tenant Jupyter Server where users have adjacent directories with predictable or shared prefixes, especially numeric username schemes. Single-user deployments or layouts without prefix-overlapping siblings have lower practical exposure.
Exploitation context
The source bundle reports authentication is required and user interaction is not. CISA KEV status is false, and the provided sources do not state active exploitation in the wild.
Researcher notes
Focus analysis on prefix-overlap directory layouts rather than generic path traversal assumptions. Evidence supports affected jupyter_server versions before 2.18.0, authenticated network access, and impact to confidentiality, integrity, and limited availability. No exploit-in-the-wild evidence is provided.
Mitigation direction
Upgrade jupyter_server to version 2.18.0 or later.
Identify all deployments running jupyter_server earlier than 2.18.0.
As a workaround, ensure sibling folder names do not share common prefixes.
Prioritize multi-tenant deployments and predictable username directory layouts.
Check vendor and distribution advisories for package-specific remediation guidance.
Validation and detection
Inventory installed jupyter_server versions across notebooks and hosted platforms.
Review configured root_dir values and sibling directory naming patterns.
Confirm patched systems reject root escape attempts in a controlled defensive test.
Review /api/contents access logs for unusual sibling-directory access patterns.
Verify file permissions limit damage if application path controls fail.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.