CVE-2026-5422

HIGHNVD 8.16.8
EchelonGraph scoreMEDIUM confidence

Score 6.8 from GitHub Security Advisory published 2026-06-02. NVD baseline CVSS 8.1; sources differ by 1.3.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
6.8(medium)
EPSS
35.7%
KEV
Not listed

Published

June 2, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jun 3, 2026
No patch confirmed yet.
generic

huntr - The world’s first bug bounty platform for AI/ML

https://huntr.com/bounties/24a36953-6490-466f-8cb2-a90d1ca56e0f

Vendor Advisories for CVE-2026-5422(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× 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 105 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-5422?
CVE-2026-5422 is a high vulnerability published on June 2, 2026. A path traversal vulnerability exists in jupyter-server version 2.17.0 due to an incorrect root directory boundary check in the getospath() function within jupyterserver/services/contents/fileio.py. The check uses startswith(root) without appending a trailing path separator, allowing sibling…
When was CVE-2026-5422 disclosed?
CVE-2026-5422 was first published in the National Vulnerability Database on June 2, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5422 actively exploited?
CVE-2026-5422 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-5422?
CVE-2026-5422 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.8.
How do I remediate CVE-2026-5422?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5422, 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

Explore the affected products and dependency analysis for CVE-2026-5422

Explore →

Is Your Infrastructure Affected by CVE-2026-5422?

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