LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
high
Sources
6

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.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-35397 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.6 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
7.6CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:NGitHub_M
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L1.65.5redhat-SADP

Vulnerability scoring details

Base CVSS 4.0 score

7.6High
CVSS 4.0 vector shape for CVE-2026-35397Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPjupyter-server: Jupyter Server: Unauthorized File Access via Path Traversal Vulnerability
other:Red Hat severity ratingcvssV3_1
  • 2026-05-05T20:01:20.132Z: Reported to Red Hat.
  • 2026-05-05T19:37:33.810Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
jupyter-serverjupyter_server< 2.18.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.