PoC Monitor
← All CVEs
CVE-2026-35397published 5 May 2026 19:37 UTCData: JSON · API

Jupyter-server jupyter_server

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.

First public PoC 2.8 daysafter publication · 8 May 2026
Public PoCs11 on GitHub
CVSS8.8high · scored by NVD · CWE-22
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

jupyter-server jupyter_server
  • < 2.18.0

Fixed in 2.18.0

Mitigation

Upgrade jupyter_server to 2.18.0 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published5 May 2026 · t = 0First public PoC8 May 2026 · t+2.8d

First public PoC 2.8 days after publication; not in CISA KEV. First PoC: HiteshGorana/susvibes-jupyter-server-cve-2026-35397 (created 8 May 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
HiteshGorana/susvibes-jupyter-server-cve-2026-35397 8 May 2026 +2.8 d 0 PoC via PoC Index
Flags · score 15
  • no network code found (normal for a local exploit)

Below the suspicion threshold (50); does not change the assessment.

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.