CVE-2025-62593: Browser-guard bypass leading to remote code execution in Ray
- Vendor
- Anyscale
CVE-2025-62593 is a browser-mediated remote code execution vulnerability affecting Ray versions earlier than 2.52.0. Ray Dashboard's browser-request middleware identifies browser traffic by checking whether the User-Agent header begins with "Mozilla." Firefox and Safari allow attacker-controlled JavaScript to modify this header, bypassing the restriction. Combined with DNS rebinding, a malicious webpage or advertisement can make a developer's browser submit malicious jobs to a local or network-accessible, unauthenticated Ray service. Submitted jobs execute arbitrary commands with the privileges of the Ray process. Ray 2.52.0 fixes the vulnerability.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary shell command execution on affected development or testing systems and reachable internal Ray instances, under the Ray process's privileges. This can expose source code, credentials, training data, and model artifacts, enable unauthorized CPU or GPU workloads, and facilitate lateral movement into accessible internal services or cloud infrastructure. Exploitation in the wild has been confirmed, although reported RondoDox attempts include an ineffective User-Agent choice that failed to bypass the browser guard.
Mitigation
If you can’t patch tonight, do this now.
Restrict Ray Dashboard and API access using authenticated proxies, firewall rules, and network segmentation. Enable Ray's optional token authentication, introduced in 2.52.0 and disabled by default. Use DNS-rebinding protections and block unnecessary Dashboard access. Loopback binding alone does not prevent this browser-mediated attack. If effective mitigations cannot be applied, discontinue affected deployments until they can be securely upgraded.
Remediation
Patch, then assume compromise.
Upgrade Ray to version 2.52.0 or later. Version 2.52.1 adds stronger browser-header testing for defense in depth. Rebuild container and deployment images containing vulnerable Ray dependencies and verify that deployed environments no longer retain older releases. Review affected systems for unexpected job submissions and unapproved commands executed by Ray processes.
Exploits
1 exploit validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2025-62593 exploited in the wild?
- Yes. As of Oct 9, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Aug 17, 2026.
- Is there a public exploit for CVE-2025-62593?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-62593, the earliest disclosed Aug 18, 2026.
- Is there a patch for CVE-2025-62593?
- Upgrade Ray to version 2.52.0 or later. Version 2.52.1 adds stronger browser-header testing for defense in depth.
- What products are affected by CVE-2025-62593?
- Anyscale Ray.
- How severe is CVE-2025-62593?
- CVE-2025-62593 has a CVSS v4 score of 9.4 (Critical) and an EPSS score of 60.2% (99th percentile) as of Oct 9, 2026.
Recent activity
92 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.