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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 15:05 UTC First seen by agentprime
- 31 Oct 2026, 15:05 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-rrxm-2pvv-m66x
- OSV: GHSA-rrxm-2pvv-m66x
- github.com/mmaitre314/picklescan/security/advisories/GHSA-rrxm-2pvv-m66x
- github.com/mmaitre314/picklescan/pull/53
- github.com/mmaitre314/picklescan/commit/70c1c6c31beb6baaf52c8db1b6c3c0e84a6f9dab
- github.com/mmaitre314/picklescan
- github.com/mmaitre314/picklescan/releases/tag/v0.0.33