Picklescan is missing detection when calling built-in Python cProfile.runctx

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2025-71378: 0.48% estimated exploitation activity in the next 30 days; percentile 41.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Using cProfile.runctx function, which is a built-in python library function to execute remote pickle file. Details The attack payload executes in the following steps: First, the attacker craft the payload by calling to cProfile.runctx function in reduce method Then when the victim after checking whether the pickle file is safe by using Picklescan library and this library doesn't dectect any dangerous functions, decide to pickle.load() this malicious pickle file, thus lead to remote code execution. PoC Impact Who is impacted? Any organization or individual relying on picklescan to detect malicious pickle files inside PyTorch models. What is the impact? Attackers can embed malicious code in pickle file that remains undetected but executes when the pickle file is loaded. Supply Chain Attack: Attackers can distribute infected pickle files across ML models, APIs, or saved Python objects. Corresponding https://github.com/FredericDT https://github.com/Qhaoduoyu

Published by the source

26 Aug 2025, 21:38 UTC

Last modified by the source

11 Sep 2026, 19:30 UTC

Source last checked

26 Oct 2026, 13:51 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9w88-8rmg-7g2p

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9w88-8rmg-7g2p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-71378

Advisory: Picklescan is missing detection when calling built-in Python cProfile.runctx
IDs: CVE-2025-71378, GHSA-9w88-8rmg-7g2p
Record: https://patchnext.com/advisories/cve-2025-71378 (revision 2, source checked 26 Oct 2026, 13:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: picklescan 0.0.30. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI picklescan: affected < 0.0.30; fixed in 0.0.30

## Suggested inspection (read-only)
- `python -m pip show picklescan`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on picklescan.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9w88-8rmg-7g2p (OSV record GHSA-9w88-8rmg-7g2p lists affected ranges: PyPI picklescan >=0 <0.0.30 (fixed))
- Verified: https://github.com/advisories/GHSA-9w88-8rmg-7g2p (GitHub-reviewed advisory GHSA-9w88-8rmg-7g2p lists affected ranges: PyPI picklescan >=0 <0.0.30)

Commands are suggestions: review each one before running it.