← Back
CVE-2025-62593
CISA KEV
high
CVSS 8.8
[KEV] Cross-Site Request Forgery (CSRF) in Ray-project ray (CVE-2025-62593)
Summary
vulnerability 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.
AI summary snake-internal / snake-material-v2
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-352 / 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.
❓ What is the problem
**CSRF** (CWE-352) exists in Ray-project ray. Attackers reach the vulnerable code path via ``fetch`` without authentication.
📍 Affected scope
Ray-project ray — . Attack surface: `fetch`.
🔥 Severity
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.
🔧 How to fix
Update to **2.52.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
4Consider incident declaration escalate
Notify SOC / on-callCISA KEV登録済 = 実環境で悪用が観測されている。Step 3 で兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。
-
6Apply patch patch
Upgrade ray to 2.52.0ステージング環境で 2.52.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
ray
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.52.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-62593
- advisory 134c704f-9b21-4f2e-91b3-4a467353bcc0
- advisory https://github.com/advisories/GHSA-q279-jhrf-cc6v
- package https://github.com/ray-project/ray
- package https://pypi.org/project/ray
- web https://github.com/ray-project/ray/commit/70e7c72780bdec075dba6cad1afe0832772bfe09
- web https://github.com/ray-project/ray/security/advisories/GHSA-q279-jhrf-cc6v
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0
- web https://github.com/nccgroup/singularity/pull/68
- web https://docs.ray.io/en/releases-2.51.1/ray-security/index.html
- web https://en.wikipedia.org/wiki/Malvertising
- web https://github.com/ray-project/ray/blob/e7889ae542bf0188610bc8b06d274cbf53790cbd/python/ray/dashboard/http_server_head.py#L184-L196
- web https://github.com/ray-project/ray/blob/f39a860436dca3ed5b9dfae84bd867ac10c84dc6/python/ray/dashboard/optional_utils.py#L129-L155