CVE-2026-32981 — ray
CVE-2026-32981 is a Path Traversal vulnerability in ray. A fix is available for ray — see the affected versions and patch details below.
Ray Dashboard <= 2.8.0 Path Traversal Leading to Local File Disclosure
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 CVE-2026-32981.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
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' |
Detection & 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 CVE-2026-32981 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-32981 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-32981. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
| 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 CVE-2026-32981 in your dependencies?
O3 Security finds CVE-2026-32981 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.