CVE-2026-35397

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 55% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track*)
EG Risk 56/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

May 5, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated May 5, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Path traversal via jupyter-server REST API allows access to a subset of directories sibling to the `root_dir` · Advisory · jupyter-server/jupyter_server · GitHub

https://github.com/jupyter-server/jupyter_server/security/advisories/GHSA-5789-5fc7-67v3

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatmta/mta-solution-server-rhel9:17841098832026-07-21redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
jupyter-server1.10.2-1 ... 2.9.1-1 (28 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
jupyter-server1.23.3-1 ... 2.9.1-1 (14 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
jupyter-server2.15.0-1, 2.17.0-1, 2.20.0-1, 2.20.0-2, 2.20.0-3
Debian:14(1)
PackageVulnerable rangeFixed inDependents
jupyter-server2.15.0-1, 2.17.0-12.20.0-1
PyPI(1)
PackageVulnerable rangeFixed inDependents
jupyter-server0.0.0 ... 2.9.1 (155 versions)2.18.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 55× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 185 total refreshes for this CVE.

  1. 2026-09-06 13:47 UTCEPSS rescore
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 13:53 UTCEPSS rescore
  5. 2026-09-01 04:39 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-28 16:48 UTCVendor advisory
  10. 2026-08-28 16:00 UTCEG score recompute
  11. 2026-08-28 16:00 UTCVendor advisory
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-23 20:42 UTCEG score recompute
  16. 2026-08-23 20:42 UTCVendor advisory
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-19 17:03 UTCEPSS rescore
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-17 13:01 UTCEG score recompute
  24. 2026-08-17 13:01 UTCVendor advisory
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 04:57 UTCEG score recompute
  2. 2026-08-16 04:57 UTCVendor advisory
  3. 2026-08-16 02:14 UTCEPSS rescore
  4. 2026-08-15 02:27 UTCEG score recompute
  5. 2026-08-15 02:27 UTCVendor advisory
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 15:01 UTCVendor advisory
  8. 2026-08-14 03:33 UTCEG score recompute
  9. 2026-08-14 03:33 UTCVendor advisory
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 04:37 UTCVendor advisory
  12. 2026-08-12 17:11 UTCEG score recompute
  13. 2026-08-12 17:11 UTCVendor advisory
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-11 16:02 UTCEG score recompute
  16. 2026-08-11 16:02 UTCVendor advisory
  17. 2026-08-11 01:35 UTCEG score recompute
  18. 2026-08-11 01:35 UTCVendor advisory
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 12:58 UTCVendor advisory
  21. 2026-08-10 01:32 UTCVendor advisory
  22. 2026-08-09 14:06 UTCEG score recompute
  23. 2026-08-09 14:06 UTCVendor advisory
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 02:39 UTCEG score recompute
  26. 2026-08-09 02:39 UTCVendor advisory
  27. 2026-08-08 16:37 UTCEPSS rescore
  28. 2026-08-08 10:10 UTCVendor advisory
  29. 2026-08-07 22:44 UTCEG score recompute
  30. 2026-08-07 22:44 UTCVendor advisory
  31. 2026-08-07 11:18 UTCVendor advisory
  32. 2026-08-06 21:44 UTCEG score recompute
  33. 2026-08-06 21:44 UTCVendor advisory
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-06 10:10 UTCVendor advisory
  36. 2026-08-05 22:24 UTCEG score recompute
  37. 2026-08-05 22:24 UTCVendor advisory
  38. 2026-08-05 19:17 UTCEPSS rescore
  39. 2026-08-04 15:10 UTCEPSS rescore
  40. 2026-08-04 10:38 UTCEPSS rescore
  41. 2026-08-03 19:56 UTCEG score recompute
  42. 2026-08-03 19:56 UTCVendor advisory
  43. 2026-08-03 10:36 UTCEPSS rescore
  44. 2026-08-03 04:42 UTCVendor advisory
  45. 2026-08-02 16:41 UTCVendor advisory
  46. 2026-08-02 05:14 UTCEG score recompute
  47. 2026-08-02 05:14 UTCVendor advisory
  48. 2026-08-02 02:27 UTCEPSS rescore
  49. 2026-08-01 04:16 UTCEPSS rescore
  50. 2026-07-30 16:28 UTCEPSS rescore
  51. 2026-07-30 01:30 UTCEPSS rescore
  52. 2026-07-27 14:13 UTCEPSS rescore
  53. 2026-07-26 14:54 UTCEPSS rescore
  54. 2026-07-26 14:54 UTCEPSS rescore
  55. 2026-07-26 08:31 UTCEG score recompute
  56. 2026-07-26 08:31 UTCVendor advisory
  57. 2026-07-25 14:18 UTCEPSS rescore
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-24 14:17 UTCEPSS rescore
  60. 2026-07-24 14:17 UTCEPSS rescore
  61. 2026-07-23 14:18 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 03:10 UTCEG score recompute
  64. 2026-07-22 14:08 UTCEPSS rescore
  65. 2026-07-21 15:24 UTCEPSS rescore
  66. 2026-07-20 23:02 UTCOSV refresh
  67. 2026-07-20 17:08 UTCEPSS rescore
  68. 2026-07-19 14:31 UTCEPSS rescore
  69. 2026-07-19 02:29 UTCEPSS rescore
  70. 2026-07-18 10:04 UTCEPSS rescore
  71. 2026-07-16 17:03 UTCEPSS rescore
  72. 2026-07-15 16:57 UTCEPSS rescore
  73. 2026-07-15 16:57 UTCEPSS rescore
  74. 2026-07-15 02:25 UTCNVD updateCVSS v3 → 8.8
  75. 2026-07-15 02:00 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-35397?
CVE-2026-35397 is a high vulnerability published on May 5, 2026. 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 rootdir and access sibling directories whose names begin with the same prefix as the rootdir. For example,…
When was CVE-2026-35397 disclosed?
CVE-2026-35397 was first published in the National Vulnerability Database on May 5, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-35397 actively exploited?
CVE-2026-35397 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.4% of all scored CVEs.
What is the CVSS score of CVE-2026-35397?
CVE-2026-35397 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-35397?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-35397, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-35397

Explore →

Is Your Infrastructure Affected by CVE-2026-35397?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.