Skip to main content

Jupyter Server EUVD-2026-33905

| CVE-2026-5422 HIGH
Relative Path Traversal (CWE-23)
2026-06-02 @huntr_ai GHSA-gf7q-q4j7-hp7c
8.1
CVSS 3.1
Share

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

6
Analysis Updated
Jun 03, 2026 - 17:28 vuln.today
v3 (cvss_changed)
Analysis Updated
Jun 03, 2026 - 17:28 vuln.today
v2 (cvss_changed)
Re-analysis Queued
Jun 03, 2026 - 17:22 vuln.today
cvss_changed
Severity Changed
Jun 03, 2026 - 17:22 NVD
MEDIUM HIGH
CVSS changed
Jun 03, 2026 - 17:22 NVD
6.8 (MEDIUM) 8.1 (HIGH)
Analysis Generated
Jun 02, 2026 - 10:20 vuln.today

DescriptionNVD

A path traversal vulnerability exists in jupyter-server version 2.17.0 due to an incorrect root directory boundary check in the _get_os_path() function within jupyter_server/services/contents/fileio.py. The check uses startswith(root) without appending a trailing path separator, allowing sibling directories with names starting with the same prefix as root_dir to bypass the check. Additionally, the to_os_path() function in utils.py does not strip ".." from path parts, enabling traversal sequences to bypass the vulnerable check. This vulnerability can lead to unauthorized read/write access to files in sibling directories, potentially exposing sensitive data in shared hosting environments.

AnalysisAI

Path traversal in Jupyter Server 2.17.0 allows authenticated users to read and write files in sibling directories outside the configured root, via a flawed startswith() boundary check in _get_os_path() combined with to_os_path() failing to strip '..' sequences. With CVSS 8.1 (high confidentiality and integrity impact) and a publicly available proof-of-concept disclosed through huntr, the issue is particularly dangerous in shared/multi-tenant hosting where multiple Jupyter instances share a parent directory. …

Sign in for full analysis, threat intelligence, and remediation guidance.

RemediationAI

Within 24 hours: Identify all Jupyter Server 2.17.0 instances, particularly in multi-tenant configurations; restrict network access to trusted sources only; review recent access logs for suspicious directory traversal patterns. Within 7 days: Implement file system restrictions (strict directory ACLs limiting process to configured root only); enable comprehensive file access auditing; isolate affected instances from other critical systems. …

Sign in for detailed remediation steps.

Vendor StatusVendor

Share

EUVD-2026-33905 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy