# CVE-2026-120833: labbench before 0.46.1 Deserialization of Untrusted Data via read() Pickle Auto-Dispatch


- **Severity:** High 8.5 (`CVSS:4.0/AV:L/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:** 3 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-4ppf-9g5f-q8hv

## What is CVE-2026-120833?

CVE-2026-120833 is a high-severity vulnerability in NIST labbench, published on 3 Nov 2026. 

### Official description

labbench before 0.46.1 contains a deserialization of untrusted data vulnerability in read() and read_relational() that passes any file with a .p or .pickle extension to pandas.read_pickle based on the extension alone. Attackers who supply a crafted data file or relational data archive can execute arbitrary code when a user loads it with these functions.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

1 open source package ship an affected version, including labbench.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `labbench` | PyPI | `pkg:pypi/labbench` | All versions | 0.46.1 |

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

Upgrade labbench to 0.46.1 or later.

## Is CVE-2026-120833 being exploited?

There is no known exploitation of CVE-2026-120833 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120833 is a high-severity vulnerability in NIST labbench, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120833 in the wild and no public exploit code.

Affected packages and fixed versions:
- labbench (PyPI): affected all versions; fixed in 0.46.1

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

## Sources

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

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