CVE-2026-32981
Path Traversal in Ray Dashboard Allows Local File Disclosure
Publication date: 2026-03-17
Last updated on: 2026-03-19
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| anyscale | ray | to 2.8.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-32981 is a path traversal vulnerability found in Ray Dashboard versions prior to 2.8.1. It occurs because the software does not properly validate or sanitize user-supplied file paths in its static file handling mechanism. This flaw allows an attacker to use traversal sequences like "../" to navigate outside the intended static directory and access local files that should be protected.'}] [2]
How can this vulnerability impact me? :
This vulnerability can lead to local file disclosure, meaning an attacker can remotely access sensitive files on the system running the Ray Dashboard without any authentication or user interaction. The impact is primarily on confidentiality, as sensitive information stored in files outside the intended directory can be exposed.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Ray Dashboard to version 2.8.1 or later, as the issue is fixed in these versions.
Additionally, consider restricting access to the Ray Dashboard service (default port 8265) to trusted networks or users to reduce exposure.