CVE-2026-32981

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 42% 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, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A path traversal vulnerability was identified in Ray Dashboard (default port 8265) in Ray versions prior to 2.8.1. Due to improper validation and sanitization of user-supplied paths in the static file handling mechanism, an attacker can use traversal sequences (e.g., ../) to access files outside the intended static directory, resulting in local file disclosure.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

March 17, 2026

Last Modified

July 22, 2026

Advisory Details (10)

Auto-updated Jul 7, 2026
Patch available. Sources: redhat.
redhat

2448440 – (CVE-2026-32981) CVE-2026-32981 ray: Ray Dashboard Path Traversal Leading to Local File Disclosure

https://bugzilla.redhat.com/show_bug.cgi?id=2448440
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-32981
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:6762
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:6761
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:5809
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:24977
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19712
generic

Ray Dashboard <= 2.8.0 Path Traversal Leading to Local File Disclosure | Advisories | VulnCheck

https://www.vulncheck.com/advisories/ray-dashboard-path-traversal-leading-to-local-file-disclosure
generic

Packet Storm

https://packetstorm.news/files/id/215801/
generic

GitHub - ray-project/ray: Ray is an AI compute engine. Ray consists of a core distributed runtime and a set of AI Libraries for accelerating ML workloads. · GitHub

https://github.com/ray-project/ray

Vendor Advisories for CVE-2026-32981(7)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-vllm-cuda-rhel9:17839987742026-07-21redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17800692222026-06-10redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17786777222026-05-20redhat
redhatrhaiis/model-opt-cuda-rhel9:17745473842026-04-07redhat
redhatrhaiis/vllm-rocm-rhel9:17752525982026-04-07redhat
redhatrhaiis/vllm-cuda-rhel9:17743511442026-03-25redhat

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
ray0.1.1 ... 2.8.0 (76 versions)2.8.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 57× 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 127 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-32981?
CVE-2026-32981 is a high vulnerability published on March 17, 2026. A path traversal vulnerability was identified in Ray Dashboard (default port 8265) in Ray versions prior to 2.8.1. Due to improper validation and sanitization of user-supplied paths in the static file handling mechanism, an attacker can use traversal sequences (e.g., ../) to access files outside…
When was CVE-2026-32981 disclosed?
CVE-2026-32981 was first published in the National Vulnerability Database on March 17, 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-32981 actively exploited?
CVE-2026-32981 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 42.2% of all scored CVEs.
What is the CVSS score of CVE-2026-32981?
CVE-2026-32981 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-32981?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32981, 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-32981

Explore →

Is Your Infrastructure Affected by CVE-2026-32981?

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

Start Free Scan →Browse All CVEs