# CVE-2025-10155: PickleScan Security Bypass Using Misleading File Extension

> Attackers can bypass security checks in picklescan by using misleading file extensions, leading to malicious code execution when the file is loaded.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2025
- **Updated:** 17 Sep 2025
- **Also known as:** GHSA-jgw4-cr84-mqxg, PYSEC-2025-151

## What is CVE-2025-10155?

CVE-2025-10155 is a critical vulnerability in mmaitre314 picklescan, published on 17 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Improper Input Validation vulnerability in the scanning logic of mmaitre314 picklescan versions up to and including 0.0.30 allows a remote attacker to bypass pickle files security checks by supplying a standard pickle file with a PyTorch-related file extension. When the pickle file incorrectly considered safe is loaded, it can lead to the execution of malicious code.

Weakness: CWE-20 (Improper Input Validation)

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

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.31 |
| `picklescan` | PyPI | All versions | 0.0.31 |
| `picklescan` | PyPI | All versions | 0.0.31 |

Products: Mmaitre314 Picklescan.

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

Upgrade picklescan to 0.0.31 or later.

## Is CVE-2025-10155 being exploited?

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

## Other vulnerabilities in mmaitre314 picklescan

- [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)
- [CVE-2025-71378](https://insights.sbomify.com/CVE-2025-71378/): picklescan - Remote Code Execution via Undetected cProfile.runctx in Pickle Files (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10155 is a critical vulnerability in mmaitre314 picklescan, published on 17 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10155 exists.

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

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

## Sources

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

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