# CVE-2024-45857: Cleanlab Deserialization of Untrusted Data vulnerability

> Attackers can execute arbitrary code by tricking users into loading a malicious pickle file in the Cleanlab library.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Sep 2024
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-8cm9-rrgc-4pcj, PYSEC-2026-1254

## What is CVE-2024-45857?

CVE-2024-45857 is a high-severity unsafe deserialization vulnerability in cleanlab, published on 12 Sep 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Deserialization of untrusted data can occur in versions 2.4.0 or newer of the Cleanlab project, enabling a maliciously crafted datalab.pkl file to run arbitrary code on an end user’s system when the data directory is loaded.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-45857?

3 open source packages ship an affected version, including cleanlab.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cleanlab` | PyPI | From 2.4.0 to 2.6.6 | None |
| `cleanlab` | PyPI | From 2.4.0 to 2.6.6 | None |
| `cleanlab` | PyPI | From 2.4.0 to 2.6.6 | None |

## How do I fix CVE-2024-45857?

No fix has been published for CVE-2024-45857 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-45857 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45857 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45857 and fix it if it is affected.

What it is: CVE-2024-45857 is a high-severity unsafe deserialization vulnerability in cleanlab, published on 12 Sep 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-45857 exists.

Affected packages and fixed versions:
- cleanlab (PyPI): affected from 2.4.0 up to 2.6.6; no fix listed
- cleanlab (PyPI): affected from 2.4.0 up to 2.6.6; no fix listed
- cleanlab (PyPI): affected from 2.4.0 up to 2.6.6; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-45857/ (Markdown: https://insights.sbomify.com/CVE-2024-45857/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45857
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45857
- OSV: https://osv.dev/vulnerability/CVE-2024-45857

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45857/
Summaries are generated and may contain mistakes; the official description above is the record.