Advisory record · GHSA-rrxm-2pvv-m66x

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

CVSS 7.6 HighEPSS 0.0048 · 41st percentile

Published by the GitHub Advisory Database at 30 Dec 2025, 15:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
picklescanPyPI<0.0.330.0.33
Identifiers
GHSA-rrxm-2pvv-m66x · CVE-2025-71372
Weakness (CWE)
CWE-94 · CWE-502
Published
30 Dec 2025
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Picklescan versions before 0.0.33 fail to flag malicious pickle files that use numpy.f2py.crackfortran.getlincoef as a gadget, so such files are reported as safe. An attacker who supplies a crafted pickle or model file can get arbitrary code execution when a victim loads it with pickle.load(). Upgrade picklescan to version 0.0.33 or later.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.6 High 4.0 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 CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0048, the 41st percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.