CVE-2026-41486: Ray: Remote Code Execution via Parquet Arrow Extension Type Deserialization
Ray Data registers custom Arrow extension types (ray.data.arrowtensor, ray.data.arrowtensorv2, ray.data.arrowvariableshapedtensor) globally in PyArrow. When PyArrow reads a Parquet file containing one of these extension types, it calls arrowextdeserialize on the field's metadata bytes.
Published Apr 24, 2026 · Updated May 13, 2026
Affected packages
ray
- Ecosystem
- PyPI
- Affected
- >= 2.49.0, < 2.55.0
- Fixed in
- 2.55.0
- Check
pip show ray
Advisory details
From the GitHub Advisory Database (CC BY 4.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.
In May 2024, Ray fixed a related vulnerability in PyExtensionType-based extension types (issue #41314, PR #45084). In July 2025, PR #54831 introduced cloudpickle.loads() into the replacement extension types' deserialization path, reintroducing the same class of vulnerability.
Impact
- Affected versions: Ray 2.49.0 through 2.54.0 (latest release as of March 2026). The vulnerable
_deserialize_with_fallbackfunction withcloudpickle.loads()was introduced in commitf6d21db1a4(PR #54831, July 2025), first released in Ray 2.49.0. - Affected configurations: Any process that uses Ray Data and reads Parquet files. The extension types are registered globally in PyArrow, so all Parquet reads in the process are affected, including
ray.data.read_parquet(),pyarrow.parquet.read_table(),pandas.read_parquet(), etc. - Attacker prerequisites: The attacker must place a crafted Parquet file where a Ray Data pipeline reads it. No authentication or cluster access is required. The Parquet file must contain a column with a
ray.data.arrow_tensor(or v2, or variable-shaped) extension type name, which makes this a targeted attack against Ray Data users.
Credited to shakevsky.
References
- https://github.com/ray-project/ray/security/advisories/GHSA-mw35-8rx3-xf9r
- https://github.com/ray-project/ray/pull/54831
- https://nvd.nist.gov/vuln/detail/CVE-2026-41486
- https://github.com/ray-project/ray/pull/62056
- https://github.com/ray-project/ray/commit/c02bd31ae31996805868baa446a131a8d304525f
- https://github.com/ray-project/ray/releases/tag/ray-2.55.0
- https://github.com/advisories/GHSA-mw35-8rx3-xf9r
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Ray vulnerabilities
All Ray entriesCVE-2026-57516
Ray: Arbitrary code execution via ray.data.read_webdataset default decoder: pickle.loads(value) and torch.load(weights_only=False)
high8.8Jul 24, 2026CVE-2026-32981
Ray Dashboard is vulnerable to path traversal through its static file handling mechanism
high7.5Mar 17, 2026CVE-2026-27482
Ray dashboard DELETE endpoints allow unauthenticated browser-triggered DoS (Serve shutdown / job deletion)
medium5.9Feb 20, 2026CVE-2025-34351
Ray's New Token Authentication is Disabled By Default
critical9.3No fixNov 27, 2025CVE-2025-62593
Ray is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding Attack
critical9.4ExploitedNov 26, 2025CVE-2025-1979
ray vulnerable to Insertion of Sensitive Information into Log File
medium6.4Mar 6, 2025
