# CVE-2025-71378: picklescan - Remote Code Execution via Undetected cProfile.runctx in Pickle Files

> Attackers can execute arbitrary code by crafting pickle files that bypass picklescan detection, requiring users to upgrade the library.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-9w88-8rmg-7g2p, PYSEC-2026-247

## What is CVE-2025-71378?

CVE-2025-71378 is a high-severity unsafe deserialization vulnerability in picklescan, published on 21 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

picklescan before 0.0.30 fails to detect cProfile.runctx function calls in pickle file reduce methods, allowing attackers to execute arbitrary code. Malicious pickle files bypass picklescan detection and execute remote code when loaded via pickle.load().

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-71378?

3 open source packages ship an affected version, including picklescan. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `picklescan` | PyPI | All versions | 0.0.30 |
| `picklescan` | PyPI | All versions | 0.0.30 |
| `picklescan` | PyPI | All versions | 0.0.30 |

Products: Mmaitre314 Picklescan.

## How do I fix CVE-2025-71378?

Upgrade picklescan to 0.0.30 or later.

## Is CVE-2025-71378 being exploited?

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

## Other vulnerabilities in picklescan

- [CVE-2025-10155](https://insights.sbomify.com/CVE-2025-10155/): PickleScan Security Bypass Using Misleading File Extension (critical 9.3)
- [CVE-2025-10156](https://insights.sbomify.com/CVE-2025-10156/): PickleScan Security Bypass via Bad CRC in ZIP Archive (critical 9.3)
- [CVE-2025-10157](https://insights.sbomify.com/CVE-2025-10157/): PickleScan Bypasses Unsafe Globals Check Using Submodule Imports (critical 9.3)
- [CVE-2025-71348](https://insights.sbomify.com/CVE-2025-71348/): picklescan - Arbitrary Code Execution via torch.utils._config_module.load_config Bypass (high 7.6)
- [CVE-2025-71357](https://insights.sbomify.com/CVE-2025-71357/): picklescan - Arbitrary Code Execution via Undetected idlelib.pyshell.ModifiedInterpreter.runcommand (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71378 and fix it if it is affected.

What it is: CVE-2025-71378 is a high-severity unsafe deserialization vulnerability in picklescan, published on 21 Jun 2026. An attacker can exploit it over the internet without logging in, 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-2025-71378 exists.

Affected packages and fixed versions:
- picklescan (PyPI): affected all versions; fixed in 0.0.30
- picklescan (PyPI): affected all versions; fixed in 0.0.30
- picklescan (PyPI): affected all versions; fixed in 0.0.30

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

## Sources

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

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