CVE-2026-5422

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

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

A fix is available — apply it.

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
8.1(medium)
EG Risk
52(Track*)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
37%
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(3)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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-1, 2.20.0-1, 2.20.0-2, 2.20.0-3——
PyPI(1)
PackageVulnerable rangeFixed inDependents
jupyter-server0.0.0 ... 2.9.1 (157 versions)2.18.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 61× 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 214 total refreshes for this CVE.

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 63.3% of all scored CVEs.
What is the CVSS score of CVE-2026-5422?
CVE-2026-5422 has a CVSS v3 base score of 8.1 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs