Ray-Project Ray Code Injection Vulnerability
ray-project — ray
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.
9.4
16.9%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- Low
- Attack requirements
- None
- Privileges required
- None
- User interaction
- Passive
- Confidentiality (Vulnerable System)
- High
- Integrity (Vulnerable System)
- High
- Availability (Vulnerable System)
- High
- Confidentiality (Subsequent System)
- High
- Integrity (Subsequent System)
- High
- Availability (Subsequent System)
- High
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
- Published
- Nov 26, 2025
- Modified
- Aug 18, 2026
- Added to KEV
- Aug 17, 2026
- Federal patch due
- Aug 20, 2026
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.
Weakness classification
Proof-of-concept & exploitation references
2 foundWeaponization
Public repositories whose name or description references CVE-2025-62593, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
- Boreas37/CVE-2025-62593-PoC★ 2
PoC for CVE-2025-62593: unauthenticated RCE in Ray (CISA KEV). Stdlib-only Python.
updated Aug 19, 2026
- maxprog-svg/CVE-2026-33017★ 0
CVE-2025-62593 — Ray Unauthenticated RCE Exploit is an unauthenticated remote code execution vulnerability in the Ray distributed AI compute engine.
updated Sep 1, 2026
References
How this class of flaw gets exploited
Frequently asked questions
What is CVE-2025-62593?
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.
How severe is CVE-2025-62593?
CVE-2025-62593 has a CVSS base score of 9.4 out of 10 (CVSS 4.0).
Is CVE-2025-62593 actively exploited in the wild?
Yes. CVE-2025-62593 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Aug 17, 2026, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2025-62593?
16.9% - meaning FIRST.org's EPSS model estimates a 16.9% probability this vulnerability will be exploited in the wild within 30 days (97% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2025-62593?
We found 2 public GitHub repositories referencing CVE-2025-62593, though none matched a known Nuclei template or Metasploit module at last check. Review each one before relying on it - see the proof-of-concept section above.
What type of vulnerability is CVE-2025-62593?
CVE-2025-62593 is classified under CWE-94, CWE-352 (CWE-94: Improper Control of Generation of Code ('Code Injection')).
Cross-checked against
Impactr finds and proves whether CVE-2025-62593 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist