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.
Original description
The description as published by the source.
Ray is an AI compute engine. From version 2.54.0 to before version 2.55.0, Ray Data registers custom Arrow extension types (ray.data.arrow_tensor, ray.data.arrow_tensor_v2, ray.data.arrow_variable_shaped_tensor) globally in PyArrow. When PyArrow reads a Parquet file containing one of these extension types, it calls arrow_ext_deserialize on the field's metadata bytes. Ray's implementation passes these bytes directly to cloudpickle.loads(), achieving arbitrary code execution during schema parsing, before any row data is read. This issue has been patched in version 2.55.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-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.
Arbitrary code execution (CWE-94) exists in ray. Attackers reach the vulnerable code path via ray.data.arrow_tensor without authentication.
Check the vendor advisory for the affected versions of ray. Attack surface: ray.data.arrow_tensor / ray.data.arrow_tensor_v2 / ray.data.arrow_variable_shaped_tensor / __arrow_ext_deserialize__.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.55.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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ray to 2.55.0ステージング環境で 2.55.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com