CVE-2025-71373: picklescan versions before 0.0.33 do not detect operator.methodcaller function calls in pickle files
Affects picklescanSource GCVE Database
Not known to be exploited · CVSS 8.1 High : upgrade to 0.0.33 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.0.33
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade picklescan to 0.0.33.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIpicklescanpkg:pypi/picklescanOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, avoid relying solely on picklescan versions before 0.0.33 for security validation of pickle files. Consider additional security controls or alternative validation methods to mitigate risk.
Description
picklescan versions before 0.0.33 do not detect operator.methodcaller function calls in pickle files, enabling attackers to bypass security checks. This allows remote attackers to craft malicious pickle payloads that execute arbitrary code when loaded, potentially compromising systems relying on picklescan for validation.