PatchTheCVEpicklescan vulnerabilities and fixes
Recent CVEs affecting picklescan, with upgrade or downgrade steps. 4 tracked.
picklescan has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2026-06-21. Highest priority: CVE-2025-71348 (score 45/100).
- CVE-2025-71348 HIGH 8.1 UPGRADE picklescan before 0.0.28 fails to detect malicious pickle files that invoke torch.utils._config_module.load_co
- CVE-2025-71378 HIGH 8.1 UPGRADE picklescan before 0.0.30 fails to detect cProfile.runctx function calls in pickle file reduce methods, allowin
- CVE-2025-71357 HIGH 8.1 UPGRADE picklescan before 0.0.30 fails to detect malicious pickle files using idlelib.pyshell.ModifiedInterpreter.runc
- CVE-2026-56304 MEDIUM 6.5 UPGRADE picklescan before 1.0.1 contains an unsafe pickle deserialization vulnerability allowing unauthenticated attac
FAQ
How do I fix picklescan vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is picklescan being exploited right now?
None of the tracked picklescan CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which picklescan CVE should I patch first?
CVE-2025-71348 currently ranks highest (45/100): picklescan before 0.0.28 fails to detect malicious pickle files that invoke torch.utils._config_module.load_co.