What is Ray CVE-2025-62593?
Ray's security advisory describes a critical remote code execution flaw affecting versions before 2.52.0. A developer running Ray who visits a malicious site in Firefox or Safari can be attacked through DNS rebinding, which sends requests to Ray's unauthenticated /api/jobs endpoint on port 8265. The guard against browser requests only checked whether the User-Agent started with "Mozilla". The browser can also be used against Ray instances on the internal network.
The advisory was published in November 2025, and CISA added CVE-2025-62593 to its Known Exploited Vulnerabilities catalog on August 17, 2026, with an August 20 due date for federal agencies. GitHub rates it CVSS 4.0 9.4; NVD's own CVSS 3.1 score is 8.8. The advisory says Chrome isn't affected.
Which Ray versions are affected?
- Ray versions before 2.52.0.
- Developer machines and clusters that run the Ray dashboard and jobs API on port 8265, which
ray start --headstarts. - Internal Ray clusters reachable from a developer's browser.
How to check if you're affected
- Run
pip show rayorray --versionin every environment that uses Ray, including notebooks and CI images. Anything below 2.52.0 is affected. - Find hosts listening on port 8265 and check whether the jobs API is reachable without authentication.
- Review job submissions to
/api/jobsfor jobs your team didn't start.
What to do now
- Upgrade to Ray 2.52.0 or later.
- Turn on the token authentication Ray added in 2.52.0. The advisory notes it's disabled by default.
- Keep the Ray dashboard off networks a browser can reach unless authentication is on.
Why local developer tools are an attack surface
Tools that bind an unauthenticated API to localhost assume nothing else can reach it. DNS rebinding breaks that assumption by turning the developer's own browser into the client. AI and data tooling often runs this way on laptops and shared notebooks, so treat local dashboards like any other service: require authentication, and don't rely on a User-Agent or origin check alone.
Where Nullify fits
How Nullify Covers This Class of Attack
Nullify moves actively exploited vulnerabilities in the dependencies and images you use up the backlog as soon as they're disclosed, and prepares the version change as a pull request for each owner to review.
The vulnerable version is set in your dependency manifests, lockfiles or images, which is where to look.
Frequently Asked Questions
Which Ray versions fix CVE-2025-62593?
Ray 2.52.0 and later. The release also adds token authentication, which is disabled by default, so turn it on as well. Any Ray version below 2.52.0 is affected.
How is Ray CVE-2025-62593 exploited?
A malicious website uses DNS rebinding to make a Firefox or Safari browser send requests to Ray's unauthenticated jobs API on port 8265, which then runs the attacker's job. The advisory says Chrome isn't affected.
Is CVE-2025-62593 exploited in the wild?
Yes. CISA added CVE-2025-62593 to its Known Exploited Vulnerabilities catalog on August 17, 2026, which means it has evidence of active exploitation. It gave US federal civilian agencies until August 20 to fix it. Treat exposed Ray instances as urgent.
Update Log
- Nov 17, 2026: page published from the primary sources linked above.