Ray-Project Ray's Code Injection Flaw Allows Remote Attackers to Execute Arbitrary Code on the Distributed ML Framework's Cluster Nodes; CISA's August 20th KEV Deadline Has Passed

Last refreshed2026-09-27

Status: KEV | Advisory ID: CVE-2025-62593

Key Details

CVE	CVE-2025-62593
Vulnerability Name	Ray-Project Ray Code Injection Vulnerability
CVSS Score / Version	8.8 (High) / CVSS v3.1
Updated	2026-09-22
CVSS Vector	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`
CVSS Prose	attack vector is network; attack complexity is low; privileges required is none; user interaction is required; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products	Ray-Project Ray and anyscale Ray
Exploitation status	Listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, indicating confirmed active exploitation.
Classified as	CWE-94 (Improper Control of Generation of Code ('Code Injection'))
KEV listing	Added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-08-17.
Exploitation prediction (EPSS)	62.46% probability of exploitation in the next 30 days (99% percentile) -- FIRST.org's EPSS model.
Federal remediation deadline	2026-08-20 (CISA KEV, Binding Operational Directive).

Affected Products, Subsystems & Sectors

Vendor	Product	Affected Versions	Patch Status
Ray-Project	Ray
anyscale	Ray

Vendor

Product

Affected Versions

Patch Status

Ray-Project

Ray

anyscale

Ray

Subsystems	General OT
Sectors	Multiple

What to Know

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.

What to Do

Monitor Ray-Project's and anyscale's web pages for any future patch releases.

References

Source	Reference
NVD	https://nvd.nist.gov/vuln/detail/CVE-2025-62593
CVE	https://www.cve.org/CVERecord?id=CVE-2025-62593

Source

Reference

NVD

https://nvd.nist.gov/vuln/detail/CVE-2025-62593

CVE

https://www.cve.org/CVERecord?id=CVE-2025-62593

KEV Required Action

Field	Value
KEV Link	https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Date Added to KEV	2026-08-17
Required Action Due Date	2026-08-20
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.

Field

Value

KEV Link

https://www.cisa.gov/known-exploited-vulnerabilities-catalog

Date Added to KEV

2026-08-17

Required Action Due Date

2026-08-20

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.