PYSEC-2026-2272
Vulnerability from pysec - Published: 2026-05-08 22:16 - Updated: 2026-07-13 05:51Ray 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.
| Name | purl | ray | pkg:pypi/ray |
|---|
{
"affected": [
{
"ecosystem_specific": {},
"package": {
"ecosystem": "PyPI",
"name": "ray",
"purl": "pkg:pypi/ray"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "2.54.0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.1.1",
"0.1.2",
"0.2.0",
"0.2.1",
"0.2.2",
"0.3.0",
"0.3.1",
"0.4.0",
"0.5.0",
"0.5.2",
"0.5.3",
"0.6.0",
"0.6.1",
"0.6.2",
"0.6.3",
"0.6.4",
"0.6.5",
"0.6.6",
"0.7.0",
"0.7.1",
"0.7.2",
"0.7.3",
"0.7.4",
"0.7.5",
"0.7.6",
"0.7.7",
"0.8.0",
"0.8.1",
"0.8.2",
"0.8.3",
"0.8.4",
"0.8.5",
"0.8.6",
"0.8.7",
"1.0.0",
"1.0.1",
"1.1.0",
"1.10.0",
"1.11.0",
"1.11.1",
"1.12.0",
"1.12.1",
"1.13.0",
"1.2.0",
"1.3.0",
"1.4.0",
"1.4.1",
"1.5.0",
"1.5.1",
"1.5.2",
"1.6.0",
"1.7.0",
"1.7.1",
"1.8.0",
"1.9.0",
"1.9.1",
"1.9.2",
"2.0.0",
"2.0.1",
"2.1.0",
"2.10.0",
"2.11.0",
"2.12.0",
"2.2.0",
"2.20.0",
"2.21.0",
"2.22.0",
"2.23.0",
"2.24.0",
"2.3.0",
"2.3.0rc0",
"2.3.1",
"2.30.0",
"2.31.0",
"2.32.0",
"2.32.0rc0",
"2.33.0",
"2.34.0",
"2.35.0",
"2.36.0",
"2.36.1",
"2.37.0",
"2.38.0",
"2.39.0",
"2.4.0",
"2.40.0",
"2.41.0",
"2.42.0",
"2.42.1",
"2.43.0",
"2.44.0",
"2.44.1",
"2.45.0",
"2.46.0",
"2.47.0",
"2.47.1",
"2.48.0",
"2.49.0",
"2.49.1",
"2.49.2",
"2.5.0",
"2.5.1",
"2.50.0",
"2.50.1",
"2.51.0",
"2.51.1",
"2.51.2",
"2.52.0",
"2.52.1",
"2.53.0",
"2.54.0",
"2.6.0",
"2.6.1",
"2.6.2",
"2.6.3",
"2.7.0",
"2.7.0rc0",
"2.7.1",
"2.7.2",
"2.8.0",
"2.8.1",
"2.9.0",
"2.9.1",
"2.9.2",
"2.9.3"
]
}
],
"aliases": [
"CVE-2026-41486",
"GHSA-mw35-8rx3-xf9r"
],
"details": "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\u0027s metadata bytes. Ray\u0027s 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.",
"id": "PYSEC-2026-2272",
"modified": "2026-07-13T05:51:14.917971Z",
"published": "2026-05-08T22:16:29.903Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/ray-project/ray/releases/tag/ray-2.55.0"
},
{
"type": "ADVISORY",
"url": "https://github.com/ray-project/ray/security/advisories/GHSA-mw35-8rx3-xf9r"
},
{
"type": "FIX",
"url": "https://github.com/ray-project/ray/commit/c02bd31ae31996805868baa446a131a8d304525f"
},
{
"type": "FIX",
"url": "https://github.com/ray-project/ray/pull/62056"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.