CVE-2026-32981

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 69% 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: cna:github_m, epss
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 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)
EPSS
56.2%
KEV
Not listed

Published

March 17, 2026

Last Modified

June 30, 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
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

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
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 8× in last 7d / 50× 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.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 04:31 UTCNVD updateCVSS v4 → 8.7
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 06:02 UTCOSV refresh
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-24 14:05 UTCEPSS rescore
  21. 2026-06-23 21:33 UTCEPSS rescore
  22. 2026-06-23 21:33 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 25 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-19 19:25 UTCEPSS rescore
  4. 2026-06-19 19:25 UTCEPSS rescore
  5. 2026-06-18 17:52 UTCEPSS rescore
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-17 17:53 UTCEPSS rescore
  8. 2026-06-16 17:52 UTCEPSS rescore
  9. 2026-06-15 17:49 UTCEPSS rescore
  10. 2026-06-14 23:18 UTCEPSS rescore
  11. 2026-06-13 23:00 UTCEPSS rescore
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-11 23:52 UTCEG score recompute
  15. 2026-06-11 23:52 UTCVendor advisory
  16. 2026-06-11 14:00 UTCEPSS rescore
  17. 2026-06-10 22:18 UTCEPSS rescore
  18. 2026-06-10 17:46 UTCEG score recompute
  19. 2026-06-10 17:46 UTCVendor advisory
  20. 2026-06-10 13:22 UTCEPSS rescore
  21. 2026-06-10 06:32 UTCEG score recompute
  22. 2026-06-10 06:32 UTCVendor advisory
  23. 2026-06-09 19:19 UTCEG score recompute
  24. 2026-06-09 19:19 UTCVendor advisory
  25. 2026-06-09 19:17 UTCOSV refresh

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 June 30, 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 56.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.