Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Picklescan is vulnerable to RCE via missing detection when calling numpy.f2py.crackfortran.param_eval

CVE-2025-71347GHSA-cffc-mxrf-mhh4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (picklescan 0.0.33), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2025-71347: 0.56% estimated exploitation activity in the next 30 days; percentile 46.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Picklescan uses numpy.f2py.crackfortran.parameval, which is a function in numpy to execute remote pickle files. Details The attack payload executes in the following steps: - First, the attacker crafts the payload by calling the numpy.f2py.crackfortran.parameval function via reduce method. - Then, when the victim checks whether the pickle file is safe by using the Picklescan library and this library doesn't detect any dangerous functions, they decide to use pickle.load() on this malicious pickle file, thus leading to remote code execution. PoC Impact Any organization or individual relying on picklescan to detect malicious pickle files inside PyTorch models. Attackers can embed malicious code in pickle file that remains undetected but executes when the pickle file is loaded. Attackers can distribute infected pickle files across ML models, APIs, or saved Python objects. Report by Pinji Chen (cpj24@mails.tsinghua.edu.cn) from the NISL lab (https://netsec.ccert.edu.cn/about) at…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-cffc-mxrf-mhh4

  2. Revision 1 · created ·

    Published from osv record GHSA-cffc-mxrf-mhh4

Agent brief

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

# Patch Next advisory brief: CVE-2025-71347

Advisory: Picklescan is vulnerable to RCE via missing detection when calling numpy.f2py.crackfortran.param_eval
IDs: CVE-2025-71347, GHSA-cffc-mxrf-mhh4
Record: https://patchnext.com/advisories/cve-2025-71347 (revision 2, source checked 26 Oct 2026, 13:36 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.33. A vendor fix does not mean a deployment is fixed.

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

## 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-cffc-mxrf-mhh4 (OSV record GHSA-cffc-mxrf-mhh4 lists affected ranges: PyPI picklescan >=0 <0.0.33 (fixed))
- Verified: https://github.com/advisories/GHSA-cffc-mxrf-mhh4 (GitHub-reviewed advisory GHSA-cffc-mxrf-mhh4 lists affected ranges: PyPI picklescan >=0 <0.0.33)

Commands are suggestions: review each one before running it.

Loading voting…