# CVE-2026-57845: Hugging Face Datasets through 5.1.0 Pickle Deserialization RCE via Pandas Builder


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-9hc7-p88p-mwm8

## What is CVE-2026-57845?

CVE-2026-57845 is a high-severity vulnerability in huggingface datasets, published on 23 Oct 2026. 

### Official description

Hugging Face Datasets through 5.1.0 contains an insecure deserialization vulnerability that allows attackers to execute arbitrary Python code by crafting a malicious pickle file loaded through the deprecated pandas packaged builder. Attackers can supply a pickle-backed dataset that is processed by Pandas._generate_tables via pandas.read_pickle() without validation, so when a victim calls datasets.load_dataset("pandas", data_files=...), the embedded __reduce__ payload executes code with the victim process's privileges.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-57845?


## How do I fix CVE-2026-57845?

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

## Is CVE-2026-57845 being exploited?

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

Public exploit code:

- https://github.com/SaiTeja-Erukude/CVE-2026-57845-hf-datasets-rce (github_poc): https://github.com/SaiTeja-Erukude/CVE-2026-57845-hf-datasets-rce

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57845 and fix it if it is affected.

What it is: CVE-2026-57845 is a high-severity vulnerability in huggingface datasets, published on 23 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57845 exists.

Affected product: huggingface datasets. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2026-57845/ (Markdown: https://insights.sbomify.com/CVE-2026-57845/index.md)
```

## Sources

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

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