CVE-2026-5422

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.8 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-06-02) is not newer than that change (2026-07-22), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

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.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 2, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jun 3, 2026
Patch available.
Web page

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(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17902609542026-09-30redhat
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 rangeFix by version rangeDependents
jupyter-server1.10.2-1 ... 2.9.1-1 (28 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-server1.23.3-1 ... 2.9.1-1 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-server2.15.0-1, 2.17.0-1, 2.20.0-1, 2.20.0-2, 2.20.0-3
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-server2.15.0-1, 2.17.0-1, 2.20.0-1, 2.20.0-2, 2.20.0-3
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
jupyter-server0.0.0 ... 2.9.1 (157 versions)
  • every version up to 2.18.2: fixed in 2.18.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 262 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 162 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-5422?
CVE-2026-5422 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-5422 published?
The CVE record for CVE-2026-5422 was published on June 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-5422 actively exploited?
CVE-2026-5422 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-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?
A fix for CVE-2026-5422 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-5422 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs