On this page
CVE Details
- Protection status: Protected by Atomicorp rules · About protection statuses
- CVE: CVE-2026-35397
- Name: CVE-2026-35397: Path traversal via jupyter-server REST API allows access to a subset of directories sibling to the
root_dir - Severity: High
- CVSS: 7.6 (v4.0) (High)
- CVSS version: 4.0
- CVSS source: GitHub_M CNA
- CVSS 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Attack vector: Network
- Attack complexity: Low
- Attack requirements: Present
- Privileges required: Low
- User interaction: None
- Vulnerable-system confidentiality: High
- Vulnerable-system integrity: High
- Vulnerable-system availability: Low
- Subsequent-system confidentiality: Negligible
- Subsequent-system integrity: None
- Subsequent-system availability: None
- Safety: Not defined
- CWE: CWE-22 — Improper Limitation of a Pathname to a Restricted Directory
- Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-126 (opens in a new tab) , CAPEC-64 (opens in a new tab) , CAPEC-76 (opens in a new tab) , CAPEC-78 (opens in a new tab) , CAPEC-79 (opens in a new tab)
- Vendor: jupyter
- Vulnerable product: jupyter server
- CVE published: 2026-05-05
- CVE last modified: 2026-08-28
- Affected versions (NVD configurations):
- jupyter server: < 2.18.0
- EPSS: 0.0062; 50.7th percentile as of 2026-11-20 (FIRST (opens in a new tab) )
- Latest Update: 2026-11-21
- Selected Rule IDs observed: 340034
- Matching rules: 1; rules with blocking actions: 1
- Would-block Rule IDs: 340034
- Request surfaces inspected: Raw request URI
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data
CVSS assessments
CVSS v4.0 · security-advisories@github.com
- Base score: 7.6
- Base severity: HIGH
- Assessment type: Secondary
- Source identifier: security-advisories@github.com
- Full 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Attack vector: Network
- Attack complexity: Low
- Attack requirements: Present
- Privileges required: Low
- User interaction: None
- Vulnerable-system confidentiality: High
- Vulnerable-system integrity: High
- Vulnerable-system availability: Low
- Subsequent-system confidentiality: Negligible
- Subsequent-system integrity: None
- Subsequent-system availability: None
- Safety: Not defined
- Exploit maturity: Not scored
CVSS v3.1 · NVD
- Base score: 8.8
- Base severity: HIGH
- Exploitability subscore: 2.8
- Impact subscore: 5.9
- Assessment type: Primary
- Source identifier: nvd@nist.gov
- Full vector:
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- Attack vector: Network
- Attack complexity: Low
- Privileges required: Low
- User interaction: None
- Scope: Unchanged
- Confidentiality impact: High
- Integrity impact: High
- Availability impact: High
- Exploit maturity: Not scored
CVSS v3.1 · redhat-SADP
- Base score: 7.1
- Base severity: HIGH
- Exploitability subscore: 1.6
- Impact subscore: 5.5
- Assessment type: Secondary
- Source identifier: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
- Full vector:
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L- Attack vector: Network
- Attack complexity: High
- Privileges required: Low
- User interaction: None
- Scope: Unchanged
- Confidentiality impact: High
- Integrity impact: High
- Availability impact: Low
- Exploit maturity: Not scored
Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.
Assessment source: NVD record (opens in a new tab) · CVE record (opens in a new tab)
CISA SSVC assessments
These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.
Provider: CISA ADP
Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
SSVC version: 2.0.3
Role: CISA Coordinator
Assessment timestamp: 2026-05-06T15:48:46.955099Z
Exploitation: poc
Automatable: no
Technical Impact: total
Provider: CISA ADP
Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
SSVC version: 2.0.3
Role: CISA Coordinator
Assessment timestamp: 2026-05-06T00:00:00+00:00
Exploitation: poc
Automatable: no
Technical Impact: total
Exploit references
The CVE source data tags these references as exploits. A reference alone does not establish reliability or active exploitation.
Vulnerable CPE configurations
cpe:2.3:a:jupyter:jupyter_server:*:*:*:*:*:*:*:*- Version end (exclusive):
2.18.0 - NVD match criteria ID:
E0B6C703-7E28-4F23-9878-E157975C32A4
- Version end (exclusive):
Vulnerability 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.
Recommended Actions
Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340034 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.
Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.
- Affected versions: jupyter-server jupyter_server version < 2.18.0.
- No specific CNA/vendor solution or workaround is included in the current CVE Record (opens in a new tab) . Review the vendor’s security advisories and supported-release guidance before making changes.
Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.
Research Notes
Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.
Public Vulnerability References
- NVD (opens in a new tab)
- CVE Record (opens in a new tab)
- Vendor advisory: https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-5789-5fc7-67v3 (opens in a new tab)
- CVE authority reference: https://access.redhat.com/errata/RHSA-2026:43038 (opens in a new tab)
- CVE authority reference: https://access.redhat.com/errata/RHSA-2026:60520 (opens in a new tab)
- CVE authority reference: https://access.redhat.com/security/cve/CVE-2026-35397 (opens in a new tab)
- CVE authority reference: https://bugzilla.redhat.com/show_bug.cgi?id=2466858 (opens in a new tab)
- CVE authority reference: https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-35397.json (opens in a new tab)
Test or Research Source
- Source: Exploit reference (github.com) (opens in a new tab)
- Tags: CVE-2026-35397, cve, exploitref, http, replay
Research Note Context
This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.
Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.
Learn More
Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.
Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:
- Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
- Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
- Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
- Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
- Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.
For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .