CVE-2025-62593: Ray is vulnerable to RCE via Safari & Firefox Browsers through DNS Rebinding Attack
Exploit probability rose from 0.01000 to 0.16888, crossing 0.10. The crossing is the event; the daily drift either side of it is not.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- CISA requires: 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. The federal deadline has passed: overdue since 2026-08-20. CISA KEVCISA's notes for this entry: github.com github.com cisa.gov cisa.gov
- Upgrade to ray 2.52.0 or later upper bounds of the CVE record's affected ranges
- Later advisories still cover the fixes above and name higher ones: ray 2.54.0 (CVE-2026-27482), 2.55.0 (CVE-2026-41486), 2.56.0 (CVE-2026-57516) OSV advisories
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
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.
- weakness
- CWE-94: Improper Control of Generation of Code ('Code Injection'); CWE-352: Cross-Site Request Forgery (CSRF)
- affected
- ray-project ray
- published ranges
- anyscale ray < 2.52.0
- first unaffected version, by branch
- ray 2.52.0
- fixed by package (from OSV advisories)
- ray (PyPI): 2.52.0 GHSA-q279-jhrf-cc6v PYSEC-2026-520
- later fixes (from OSV advisories)
- ray 2.52.0 is inside a range CVE-2026-27482 (GHSA-q5fh-2hc8-f6rq) lists as affected. That advisory is fixed in 2.54.0.ray 2.52.0 is inside a range CVE-2026-41486 (GHSA-mw35-8rx3-xf9r) lists as affected. That advisory is fixed in 2.55.0.ray 2.52.0 is inside a range CVE-2026-57516 (GHSA-hhrp-gw25-jr43) lists as affected. That advisory is fixed in 2.56.0.
- severity
- 9.4 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- assigned by
- GitHub_M
- published
- 2025-11-26
check us github.com github.com
Authority held, dated
- CISA KEV
- listed
- added
- 2026-08-17
- remediation due
- 2026-08-20
- ransomware use
- unknown
- remediation status
- overdue since 2026-08-20
- exploit code
- 1 public proof-of-concept repository, first seen 2026-08-18 (PoC-in-GitHub).
A KEV listing is an assertion of observed exploitation. It is the only element on this page that makes that claim.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 27 Nov 2025 | 0.00021 | |
| 2 Dec 2025 | 0.00028 | |
| 18 Dec 2025 | 0.00009 | |
| 28 Dec 2025 | 0.0001 | |
| 15 Jun 2026 | 0.00355 | scoring model v2026.06.15 |
| 18 Aug 2026 | 0.01015 | |
| 22 Aug 2026 | 0.01 | |
| 28 Aug 2026 | 0.16888 | crossed 0.10 |
| 27 Sep 2026 | 0.62459 | crossed 0.50 |
19 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Listed, added 2026-08-17. Due 2026-08-20. A changed deadline or a change in ransomware use changes this brief.
- exploit probability
- 0.62 on 2026-09-27 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 90% (0.90). Crossing a line changes this brief.
- fix
- Held: ray 2.52.0. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2025-62593', '2026-10-29T23:59:59.999999Z', now());