picklescan Known Vulnerabilities & Fixes
picklescan has 13 known security vulnerabilities in PyPI (Python). Upgrade to version 1.0.4 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 1.0.4
Upgrading to 1.0.4 or later resolves all 13 known vulnerabilities in picklescan. Run: pip install "picklescan>=1.0.4"
Is picklescan in your project?
Check if you're affected and upgrade to 1.0.4 to stay secure.
Security Summary
- 13 affected version ranges have been identified across these 13 advisories.
- 100% of known issues have a published fixed version.
- Remediation: pip install --upgrade picklescan
Vulnerabilities
13 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details. First disclosed Aug 12, 2025, most recently Mar 3, 2026 (204 days apart).
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2026-3490 PickleScan's pkgutil.resolve_name has a universal blocklist bypass | CRITICAL | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+35 more) | 1.0.4 |
| CVE-2026-56315 PickleScan has multiple stdlib modules with direct RCE not in blocklist | CRITICAL | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+35 more) | 1.0.4 |
| CVE-2026-53873 PickleScan's profile.run blocklist mismatch allows exec() bypass | CRITICAL | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+35 more) | 1.0.4 |
| CVE-2025-10156 | CRITICAL | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+26 more) | 0.0.31 |
| CVE-2026-53874 picklescan missing detection by simple obfuscation of a `builtins.eval` call | HIGH | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+32 more) | 1.0.1 |
| CVE-2025-71320 Picklescan has Incomplete List of Disallowed Inputs | HIGH | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+28 more) | 0.0.33 |
| CVE-2025-71323 Picklescan does not block ctypes | HIGH | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+28 more) | 0.0.33 |
| CVE-2025-71321 Picklescan vulnerable to Arbitrary File Writing | HIGH | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+28 more) | 0.0.33 |
| CVE-2025-71325 Picklescan has pickle parsing logic flaw that leads to malicious pickle file bypass | HIGH | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+22 more) | 0.0.27 |
| CVE-2025-71367 Picklescan is vulnerable to RCE via missing detection when calling built-in python _operator.attrgetter | HIGH | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+29 more) | 0.0.34 |
| CVE-2025-71375 Picklescan is vulnerable to RCE via missing detection when calling built-in python _operator.methodcaller | HIGH | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+29 more) | 0.0.34 |
| CVE-2025-71362 Picklescan missing detection when calling numpy.f2py.crackfortran.getlincoef | HIGH | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+28 more) | 0.0.33 |
| CVE-2025-71372 Picklescan is vulnerable to RCE via missing detection when calling numpy.f2py.crackfortran.getlincoef | HIGH | 0.0.1, 0.0.10, 0.0.11, 0.0.12 (+28 more) | 0.0.33 |
About This Data
Vulnerability data for picklescan is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related PyPI (Python) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of picklescan.