← Back
CVE-2026-41486
high
CVSS 8.8
Code Injection in ray (CVE-2026-41486)
Summary
code injection in ray (CVE-2026-41486). Successful exploitation can lead to full system takeover. Exploitable via ``ray.data.arrow_tensor``. Mitigation: upgrade to `2.55.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41486** has been found in ray.
Attackers can target a specific entry point like ``ray.data.arrow_tensor`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade ray to **2.55.0** or later.
If unsure, ask your IT team or search "ray CVE-2026-41486" on the vendor's site.
CVE-2026-41486 (ray) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `ray.data.arrow_tensor` / `ray.data.arrow_tensor_v2` / `ray.data.arrow_variable_shaped_tensor` / `__arrow_ext_deserialize__`
Patched: `2.55.0` — apply immediately
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
**arbitrary code execution** (CWE-94) exists in ray. Attackers reach the vulnerable code path via ``ray.data.arrow_tensor`` without authentication.
📍 Affected scope
ray — . Attack surface: `ray.data.arrow_tensor` / `ray.data.arrow_tensor_v2` / `ray.data.arrow_variable_shaped_tensor` / `__arrow_ext_deserialize__`.
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.55.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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade ray to 2.55.0ステージング環境で 2.55.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
ray
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.55.0"}]}]
PyPI
ray
[{"type":"ECOSYSTEM","events":[{"introduced":"2.49.0"},{"fixed":"2.55.0"}]}]