GHSA-r8g5-cgf2-4m4m: Picklescan missing detection when calling numpy.f2py.crackfortran.getlincoef
Summary An unsafe deserialization vulnerability allows an attacker to execute arbitrary code on the host when loading a malicious pickle payload from an untrusted source. Details The numpy.f2py.crackfortran module exposes many functions that call eval on arbitrary strings of values. This is the case for getlincoef and evallength. This list is probably not exhaustive.
Published Dec 29, 2025
Affected packages
picklescan
- Ecosystem
- PyPI
- Affected
- < 0.0.33
- Fixed in
- 0.0.33
- Check
pip show picklescan
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
An unsafe deserialization vulnerability allows an attacker to execute arbitrary code on the host when loading a malicious pickle payload from an untrusted source.
Details
The numpy.f2py.crackfortran module exposes many functions that call eval on arbitrary strings of values. This is the case for getlincoef and _eval_length. This list is probably not exhaustive.
According to https://numpy.org/doc/stable/reference/security.html#advice-for-using-numpy-on-untrusted-data, the whole numpy.f2py should be considered unsafe when loading a pickle.
PoC
from numpy.f2py.crackfortran import getlincoef
class EvilClass:
def __reduce__(self):
payload = "__import__('os').system('echo \"successful attack\"')"
return getlincoef, (payload, [])Impact
Who is impacted? Any organization or individual relying on picklescan to detect malicious pickle files from untrusted sources. 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.
Note
The problem was originally reported to the joblib project, but this was deemed unrelated to joblib itself. However, I checked that picklescan was indeed vulnerable.
References
- https://github.com/mmaitre314/picklescan/security/advisories/GHSA-r8g5-cgf2-4m4m
- https://github.com/mmaitre314/picklescan/pull/53
- https://github.com/mmaitre314/picklescan/commit/70c1c6c31beb6baaf52c8db1b6c3c0e84a6f9dab
- https://github.com/mmaitre314/picklescan/releases/tag/v0.0.33
- https://github.com/advisories/GHSA-r8g5-cgf2-4m4m
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-3490
PickleScan's pkgutil.resolve_name has a universal blocklist bypass
critical10.0Mar 3, 2026CVE-2026-53873
PickleScan's profile.run blocklist mismatch allows exec() bypass
critical9.8Mar 3, 2026CVE-2026-56315
PickleScan has multiple stdlib modules with direct RCE not in blocklist
critical9.8Mar 3, 2026CVE-2026-53875
Picklescan (scan_pytorch) Bypass via dynamic eval MAGIC_NUMBER
high7.1Feb 18, 2026CVE-2026-53874
picklescan missing detection by simple obfuscation of a `builtins.eval` call
high8.9Feb 2, 2026GHSA-m7j5-r2p5-c39r
picklescan vulnerable to arbitrary file create using logging.FileHandler
medium5.5Feb 2, 2026
