Tia N.List

KEV catalog · CISA Known Exploited Vulnerabilities

CVE-2025-62593 8.8
Ray-Project · Ray · Added 2026-08-17 · Published 2025-11-26
3-Day Required PoC Available KEV Automatable Active Exploitation

Details

VulnerabilityRay-Project Ray Code Injection Vulnerability
VendorRay-Project
ProductRay
Date added2026-08-17
Due date2026-08-20
Required actionApply 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.
CWECWE-352 CWE-94
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Descriptions

KEV: 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.

NVD: 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.

Compliance SSVC + BOD 26-04

Automatableyes
Technical impacttotal
Exploitation statusactive
3-day qualifyingYes
Public timeline3 days + forensic
Non-public timeline3 days + forensic
Forensic (public)Required
Forensic (non-public)Required

Research metadata

Last researched2026-08-18 12:27 UTC
Wall time0.9s
Searches6
Component defaultyes

QC notes

warn component_extraction: Component 'Ray Dashboard is_browser_request() User-Agent header check in optional_utils.py' matches or contains product name 'Ray' — no specific component identified

Hunting hypothesis agent

Hunt for DNS rebinding on Ray dashboard User-Agent bypass — attacker sites rebind to localhost, exploit Mozilla prefix to reach unauthenticated /api/jobs and execute code via Firefox or Safari

Research details

ComponentRay Dashboard is_browser_request() User-Agent header check in optional_utils.py
PreconditionsDeveloper running Ray head node with dashboard enabled on localhost:8265; attacker performs DNS rebinding via malicious website or malvertising to bypass localhost restriction; victim uses Firefox or Safari browser (Chrome not vulnerable due to non-spec User-Agent behavior); no authentication required on Ray API endpoints /api/jobs and /api/job_agent/jobs/; Ray version < 2.52.0 agent
DeliveryDNS rebinding via malicious website or malvertising redirecting browser requests to localhost Ray dashboard
Public PoCyes
Exploit notesCVSS v3 attack complexity: LOW (AV:N/AC:L) | CVSS 4.0 score: 9.4 Critical | Exploitation confirmed via RondoDox botnet (Bitsight research); NCC Group Singularity DNS rebinding tool used in PoC
SummaryRay-Project Ray prior to 2.52.0 contains a code injection vulnerability in the dashboard's User-Agent header check that allows remote code execution via DNS rebinding. Attackers exploit the weak Mozilla User-Agent validation to reach unauthenticated API endpoints from a malicious webpage in Firefox or Safari. A public PoC using NCC Group Singularity is available, and CISA confirms active exploitation in the wild. Patched in Ray 2.52.0.

Tia coverage

First reported2026-08-11
First exploit report2026-08-18
Exploit report → KEV1 days after the listing

When Tia's reporting first covered this CVE and whether a report claimed exploitation before the KEV listing. Lead-time deltas are measured from the exploitation report only — plain coverage is not exploitation intel. See the story links under Mentioned in for coverage detail.

Mentioned in

august-2026-cve-landscapecisa-warns-of-critical-ray-rce-flaw-exploited-in-active-attackssap-patches-critical-code-injection-memory-corruption-vulnerabil

Record schema v1.0. Enrichment is research-grade, not a substitute for analyst review.

Source on GitHub