Live › vulnerability › CVE-2025-62593
Go to dashboardRay's dashboard job API (port 8265) has no authentication. Its only browser defense checks that the User-Agent starts with 'Mozilla', and Firefox and Safari let a web page change that header. A page the developer visits can use DNS rebinding to submit a job and run arbitrary commands on the dev machine. It can also be used to reach Ray instances on the private network. Chrome is not affected. CISA lists it as exploited.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 5h before NVD. All times on this page are UTC.
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Ray-Project Ray | vendor | – | – |
| ray | pip | < 2.52.0 | 2.52.0, 2.52.1, 2.51.2 |
| anyscale ray | vendor | < 2.52.0 | 2.52.0 |
pip show ray or python -c "import ray; print(ray.__version__)" in every environment, including venvs, containers and notebooks2.52.0 are vulnerabless -ltnp | grep 8265 or lsof -i :8265 to see whether a Ray dashboard is listeningray job list or the dashboard's Jobs tab2.52.02.52.0 or higher. 2.52.1 and 2.51.2 add stronger browser-header rejection (Sec-Fetch-* and other headers). 2.52.0 also adds token authentication, which is off by defaultEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Ray is an AI compute engine. Prior to version 2.52.0, developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari. This vulnerability is due to an insufficient guard against browser-based attacks, as the current defense uses the User-Agent header starting with the string "Mozilla" as a defense mechanism. This defense is insufficient as the fetch specification allows the User-Agent header to be modified. Combined with a DNS rebinding attack against the browser, and this vulnerability is exploitable against a developer running Ray who inadvertently visits a malicious website, or is served a malicious advertisement (malvertising). This issue has been patched in version 2.52.0.
This page as .md · .json · in your agent: get_signal("CVE-2025-62593")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.