Ray Dashboard is vulnerable to path traversal through its static file handling mechanismGHSA-j3mh-qmjj-xp83
HIGHGHSA-j3mh-qmjj-xp83 is a high-severity (CVSS 7.5) Path Traversal vulnerability in ray. A fix is available for ray — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for GHSA-j3mh-qmjj-xp83.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
rayReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | ray | all versions | 2.8.1pip install --upgrade 'ray==2.8.1' |
Affected Products
rayanyscaleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ray, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ray to 2.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j3mh-qmjj-xp83 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for GHSA-j3mh-qmjj-xp83 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat AI Inference Server 3.2 | rhaiis/vllm-cuda-rhel9:1774351144 | RHSA-2026:5809 |
| Red Hat AI Inference Server 3.2 | rhaiis/model-opt-cuda-rhel9:1774547384 | RHSA-2026:6761 |
| Red Hat AI Inference Server 3.2 | rhaiis/vllm-rocm-rhel9:1775252598 | RHSA-2026:6762 |
| Red Hat OpenShift AI 2.25 | rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9:1780078312 | RHSA-2026:24977 |
| Red Hat OpenShift AI 2.25 | rhoai/odh-vllm-cuda-rhel9:1783998774 | RHSA-2026:42644 |
| Red Hat OpenShift AI 3.3 | rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9:1778677779 | RHSA-2026:19712 |
Frequently Asked Questions
Is GHSA-j3mh-qmjj-xp83 in your dependencies?
Find it across PyPI, including transitive dependencies.