CVE-2025-62593
CVE-2025-62593 is a security flaw in Ray-Project Ray. A booby-trapped web page can run an attacker's code through Ray-Project Ray. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 17 Aug 2026.[1]
Ray-Project Ray is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Ray-Project has published a fix or advice.
Description
CISA calls it a code injection in Ray-Project Ray. In its words: “Ray-Project Ray contains a code injection vulnerability that could allow remote code execution. Developers using Ray as a development tool may be exposed to this vulnerability exploitable through Firefox and Safari.”[1]
The CVE record adds: “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.”[2]
The underlying weakness is code injection (CWE-94), cross-site request forgery (CWE-352), in MITRE’s list of common software weaknesses.
It scores 8.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by NVD using CVSS 3.1.[2]
Affected versions
NVD’s record doesn’t list version ranges for it; Ray-Project’s advisory has them[3]. CISA names the product as Ray-Project Ray.
Most families won’t have Ray-Project Ray; it’s for whoever looks after IT at work.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 17 Aug 2026, 264 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 20 Aug 2026 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 60%. That’s in the top 1% of the flaws it scores.[4]
CISA assesses it as automatable: attackers can run it against many targets at once.
CISA doesn’t say who was attacked, or how.
Fix
Ray-Project has published a fix or advice.[3] 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).”[1]
- Check whether you use it.Ray-Project Ray is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
- Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 20 Aug 2026 to fix it.
- If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.
You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 8.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at 60%.[4] |
See also
Other code injection flaws
- CVE-2026-0322, Palo Alto Networks PAN-OS: code injection ·
- CVE-2026-65660, Microsoft SharePoint: code injection ·
- CVE-2026-60004, Gitea: code injection ·
- CVE-2026-72530, TrueConf Server: code injection ·
- CVE-2026-9198, IBM Langflow: code injection ·
References
- ^ Cybersecurity and Infrastructure Security Agency. “Ray-Project Ray Code Injection Vulnerability”. Known Exploited Vulnerabilities Catalog, added 17 Aug 2026.
- ^ National Institute of Standards and Technology. “CVE-2025-62593 Detail”. National Vulnerability Database, published 26 Nov 2025.
- ^ Ray-Project. Advisories and fixes: github.com.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.602, percentile 99.1, 31 Oct 2026.
- CVE Program. “CVE-2025-62593”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.