Ray
Ray is vulnerable to RCE via Safari & Firefox Browsers through DNS Rebinding Attack
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.52.0
Fixed in 2.52.0
Mitigation
Upgrade ray to 2.52.0 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 265 days after publication; added to CISA KEV 264 days after publication. First PoC: Boreas37/CVE-2025-62593-PoC (created 18 Aug 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs · 1 informational
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Boreas37/CVE-2025-62593-PoC | 18 Aug 2026 +265 d | 2 | PoC |
Informational 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| maxprog-svg/CVE-2026-33017 | 1 Sep 2026 +279 d | 0 | Informational · write-up |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: Ray < 2.52.0 - Remote Code Execution | 8 Sep 2026 | 14 Nov 2026 |
PoC characteristics
What to hunt for in your logs · from 1 PoC repoPOST /api/jobs/
- Content-Type
application/json- Ports
- 8265
- PoC User-Agent
Python-urllib/3.x (default)- Seen in
- 1 repo: Boreas37/CVE-2025-62593-PoC
- Evidence
- Boreas37/CVE-2025-62593-PoC/ray_rce_poc.py:77-80 Boreas37/CVE-2025-62593-PoC/README.md:26
Regex
Generated from PoC characteristics; not yet reviewed. Matches the request path and query.
(?i)^/api/jobs/(?:[?#].*)?$
Suricata
Template generated from PoC characteristics. Review before deploying.
alert http any any -> $HOME_NET [8265] (msg:"GG PoC-Monitor CVE-2025-62593 ray-project ray exploit attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/jobs/"; reference:url,poc.griffinguard.io/cve/CVE-2025-62593; classtype:web-application-attack; sid:9170000; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
title: ray-project ray exploit attempt (CVE-2025-62593)
id: gg-pocmon-cve-2025-62593-9170000
status: experimental
description: Request pattern taken from public PoCs for CVE-2025-62593. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2025-62593
logsource:
category: webserver
detection:
selection:
cs-method: POST
cs-uri-stem|contains|all:
- '/api/jobs/'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: critical
tags:
- attack.initial_access
- attack.t1190
- cve.2025.62593