Ray-Project Ray: code execution flaw under attack

What is affected

Ray-Project Ray is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.

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.

What an attacker can do

This is a code execution flaw. It lets an attacker run their own commands or programs on the affected system. In practice that usually means taking it over: installing malware, stealing data or using it to reach other devices on the same network.

How it is reached

Over the internet or network

Access the attacker needs

No account needed

Does the victim have to do something?

Yes, ordinary use is enough

What to do

1. At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
2. If you administer Ray-Project Ray at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
3. If the product is past its support date and no fix exists, take it off the internet or retire it.

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.

Vendor advisories and fixes

• github.comgithub.com/ray-project/ray/security/advisories/GHSA-q279-jhrf-cc6v
• github.comgithub.com/ray-project/ray/commit/70e7c72780bdec075dba6cad1afe0832772bfe09

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on August 17, 2026, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by August 20, 2026, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 62% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 99.2% of all scored vulnerabilities.

Its CVSS severity score is 9.4 out of 10 (critical), as recorded in the US National Vulnerability Database.

Technical description

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.