[KEV] Code Injection in Ray-Project Ray (CVE-2025-62593)
Summary
Code injection in Ray-Project Ray (CVE-2025-62593). Successful exploitation can lead to full system takeover. Exploitable via fetch. Listed in CISA KEV — actively exploited. Mitigation: upgrade to 2.52.0 or later.
Original description
The description as published by the source.
Summary
Developers working with Ray as a development tool can be exploited via a critical RCE vulnerability exploitable via Firefox and Safari.
Due to the longstanding decision by the Ray Development team to not implement any sort of authentication on critical endpoints, like the /api/jobs & /api/job_agent/jobs/ has once again led to a severe vulnerability that allows attackers to execute arbitrary code against Ray. This time in a development context via the browsers 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).
Details
The mitigations implemented to protect against browser based attacks against local Ray nodes are insufficient.
Current Mitigation Strategies
def is_browser_request(req: Request) -> bool:
"""Checks if a request is made by a browser like user agent.
This heuristic is very weak, but hard for a browser to bypass- eg,
fet…
Source: CISA Known Exploited Vulnerabilities NVD GitHub Advisory CISA KEV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-62593 has been found in Ray-Project Ray.
Attackers can target a specific entry point like fetch over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: upgrade Ray-Project Ray to 2.52.0 or later.
If unsure, ask your IT team or search "Ray-Project Ray CVE-2025-62593" on the vendor's site.
CVE-2025-62593 (Ray-Project Ray) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: fetch
Patched: 2.52.0 — apply immediately
Listed in CISA KEV — actively exploited, treat as top priority.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in Ray-Project Ray. Attackers reach the vulnerable code path via fetch without authentication.
Check the vendor advisory for the affected versions of Ray-Project Ray. Attack surface: fetch.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover. Listed in CISA KEV — actively exploited in the wild, treat as top priority.
Update to 2.52.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ray' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ray' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
rayを grep し、稼働しているサービス・バージョンを把握する。 -
2Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
3Apply patch patch
Upgrade Ray-Project Ray to 2.52.0ステージング環境で 2.52.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory NVD
- advisory bitsight.com
- advisory github.com
- exploit security-advisories@github.com
- package github.com
- package pypi.org
- patch security-advisories@github.com
- web cisa.gov
- web github.com
- web docs.ray.io
- web en.wikipedia.org
- web github.com
- web github.com