Known exploited vulnerability

CVE-2025-62593

criticalCVSS 4.0 9.4In CISA KEVEPSS 60%Published · ray-project

The short answer

CVE-2025-62593 affects ray-project ray and is rated critical (CVSS 9.4). CISA added it to the Known Exploited Vulnerabilities catalog on 2026-08-17: attackers are using it, so patch it first. Fixed versions are published for ray (2.52.0).

What it is

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, CWE-352.

Severity

9.4 critical

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Exploited (CISA KEV)

Yes, since Aug 17, 2026

Federal due date Aug 20, 2026

EPSS, next 30 days

60%

Higher than 99% of scored CVEs

How it can be exploited

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
Passive
Confidentiality impact
High
Integrity impact
High
Availability impact
High

What CISA says to do

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…

Affected packages and fixed versions

PackageEcosystemFixed inAdvisory
rayPyPI2.52.0GHSA-q279-jhrf-cc6v

Is it in your code? Drop your lockfile into the free vulnerability check, or let vulnerability watch check your repository every day and open the upgrade as a pull request.

Affected products

ray. NVD's record lists the exact affected versions.

References

Questions

Is CVE-2025-62593 being exploited?

Yes. CISA added CVE-2025-62593 to its Known Exploited Vulnerabilities catalog on 2026-08-17, with a federal remediation due date of 2026-08-20.

How do I fix CVE-2025-62593?

Upgrade to a fixed version: ray (PyPI) 2.52.0. CISA's 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…

From NVD, CISA KEV, FIRST EPSS and OSV.dev, checked . Status on NVD: Analyzed. The description is NVD's text, quoted as published.

Related

Know the day a CVE lands in your code

Connect a GitHub repository and ZeusQA checks its dependencies daily, briefs each advisory and opens the fix. Three test runs free, no card.