Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-32981: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in ray-project Ray

0
High
VulnerabilityCVE-2026-32981cvecve-2026-32981cwe-22
Published: Tue Mar 17 2026 (03/17/2026, 19:33:50 UTC)
Source: CVE Database V5
Vendor/Project: ray-project
Product: Ray

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.

AI-Powered Analysis

AILast updated: 03/17/2026, 20:12:43 UTC

Technical Analysis

CVE-2026-32981 is a path traversal vulnerability classified under CWE-22, discovered in the Ray Dashboard component of the ray-project Ray software prior to version 2.8.1. The vulnerability stems from inadequate validation and sanitization of user-supplied file paths in the static file serving mechanism on the dashboard, which by default listens on port 8265. Attackers can exploit this flaw by crafting requests containing directory traversal sequences (e.g., '../') to escape the intended static file directory and access arbitrary files on the host system. This results in unauthorized local file disclosure, potentially exposing sensitive configuration files, credentials, or other critical data. The vulnerability is remotely exploitable over the network without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector (AV:N/AC:L/AT:N/UI:N/VC:H/VI:N/VA:N) reflects a high severity with a base score of 8.7, emphasizing the ease of exploitation and high confidentiality impact. Although no active exploits have been reported, the widespread use of Ray in AI and distributed computing environments makes this a significant concern. The issue was publicly disclosed on March 17, 2026, and fixed in Ray version 2.8.1. No official patch links were provided in the source data, but upgrading to the fixed version is the primary remediation step.

Potential Impact

The primary impact of CVE-2026-32981 is unauthorized disclosure of local files on systems running vulnerable versions of Ray with the dashboard exposed. This can lead to leakage of sensitive information such as configuration files, credentials, private keys, or proprietary data, which attackers can leverage for further compromise or lateral movement. Since the vulnerability requires no authentication or user interaction, any exposed Ray Dashboard instance is at risk from remote attackers. Organizations relying on Ray for AI workloads, distributed computing, or data analytics may face data breaches, intellectual property theft, or operational disruptions. The confidentiality breach could also undermine trust and compliance with data protection regulations. Although the vulnerability does not directly enable code execution or denial of service, the information gained can facilitate more severe attacks. The scope includes all affected Ray deployments with accessible dashboards, particularly in cloud environments, research institutions, and enterprises using Ray for scalable computing.

Mitigation Recommendations

To mitigate CVE-2026-32981, organizations should immediately upgrade Ray to version 2.8.1 or later, where the path traversal vulnerability is addressed. Until upgrades can be applied, restrict network access to the Ray Dashboard port (8265) using firewalls, VPNs, or network segmentation to limit exposure to trusted users only. Implement additional input validation and sanitization controls on any custom integrations or proxies handling Ray dashboard requests. Monitor logs for suspicious requests containing directory traversal patterns (e.g., '../') targeting the dashboard. Employ host-based intrusion detection systems to detect anomalous file access patterns. Conduct regular security assessments of Ray deployments to ensure no unauthorized file access has occurred. Educate DevOps and security teams on the risks of exposing internal dashboards without proper access controls. Finally, maintain an inventory of Ray versions in use and apply security updates promptly.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-03-17T11:31:56.956Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69b9b25d771bdb1749d33708

Added to database: 3/17/2026, 7:58:21 PM

Last enriched: 3/17/2026, 8:12:43 PM

Last updated: 3/18/2026, 6:53:35 AM

Views: 12

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses