CVE-2025-62593: Ray dashboard/jobs API RCE via DNS rebinding from Firefox/Safari

Exploited in the wild Critical 9.4 EPSS 60.2%

Ray before 2.52.0 has no authentication on critical endpoints such as /api/jobs and blocks browser attacks only by rejecting User-Agent values starting with 'Mozilla', which Firefox and Safari let web pages change. Combined with DNS rebinding, a malicious website or ad visited by a developer running Ray can submit jobs and execute arbitrary code, or use the browser to attack Ray clusters on the internal network. Fixed in Ray 2.52.0; CISA added it to the Known Exploited Vulnerabilities catalog on 2026-08-17.

CVE-2025-62593CVE identifier
9.4CVSS 4.0 base score (critical)
2026-08-17added to CISA's exploited list (US federal deadline 2026-08-20)
60.2%EPSS: chance of exploitation in the next 30 days (higher than 99% of CVEs)
2025-11-26published

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

Check whether you run the affected software and which version (commands below).
Install the fixed version for your system: see “Patch it” below.
Restart the Ray head and worker nodes (ray stop / ray start) so the dashboard and job server run the new version.
If you cannot patch today, apply the temporary mitigation below and patch as soon as possible.
Because this flaw is being exploited, also check the server for signs of compromise.

Affected and fixed versions

Affected:

Ray before 2.52.0

Fixed in:

Ray 2.52.0

Am I affected?

pip show ray | grep -i ^version

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Built from source

pip install --upgrade 'ray>=2.52.0'
ray stop
ray start --head   # restart with your usual options

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

If you cannot patch yet

Ray 2.52.0 also adds an optional token authentication feature (disabled by default); enabling it further hardens the dashboard and job APIs (vendor advisory, see Ray token-auth docs).

CISA required action: 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.

https://github.com/ray-project/ray/security/advisories/GHSA-q279-jhrf-cc6v ; https://github.com/ray-project/ray/commit/70e7c72780bdec075dba6cad1afe0832772bfe09 ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2025-62593

Sources

Page generated automatically from official sources on 2026-11-03 18:05 UTC and reviewed by an editor. Always confirm with your vendor's advisory.