Ray Dashboard <= 2.8.0 : Traversal de chemin menant à une divulgation de fichier local

The primary impact of this vulnerability is the potential for local file disclosure. An attacker could leverage the path traversal sequences (e.g., ../../) to navigate outside the intended static directory and access arbitrary files on the server hosting the Ray Dashboard. This could include configuration files, source code, or other sensitive data. The blast radius is limited to the server hosting the dashboard and the files accessible from that server. While not directly leading to remote code execution, the disclosed information could be used to further compromise the system or reveal valuable insights into the Ray cluster's configuration and operation.

Organizations deploying Ray clusters with the Ray Dashboard enabled are at risk, particularly those running versions 0.0 through 2.8.1. Shared hosting environments where multiple users share the same Ray Dashboard instance are especially vulnerable, as an attacker could potentially access files belonging to other users.

• python / server:

import os
import requests

url = 'http://your_ray_dashboard_ip:8265/static/../../../../etc/passwd'
response = requests.get(url)

if response.status_code == 200:
    print('Potential Path Traversal Detected: ', response.text[:100]) # Print first 100 chars
else:
    print('No Path Traversal Detected')

• linux / server:

find / -name 'ray_dashboard.conf' -print 2>/dev/null | while read file;
do
  grep -q 'path_traversal_bypass' $file && echo "Potential Path Traversal Configuration Found: $file";
done

1. 2026-03-17Disclosure

   disclosure

1. Réservé2026-03-17
2. Publiée2026-03-17
3. EPSS mis à jour2026-03-25

The recommended mitigation is to immediately upgrade the Ray Dashboard to version 2.8.1 or later. If upgrading is not immediately feasible, consider implementing a Web Application Firewall (WAF) rule to block requests containing traversal sequences (e.g., ../, ../../). Additionally, restrict access to the Ray Dashboard to trusted networks and users. Regularly review and audit file permissions within the static directory to ensure that only authorized files are accessible. Implement input validation and sanitization on all user-supplied paths to prevent future path traversal vulnerabilities.