picklescan before 0.0.29 fails to detect malicious pickle files that exploit idlelib.autocomplete.AutoComplete.get_entity function in reduce methods. Attackers can embed undetected code in pickle files that executes arbitrary commands when loaded by victims using pickle.load().
CVE-2025-71358
This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(medium)
- EG Risk
- 52(Track*)EG Risk 52/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS
- 16.3%
- KEV
- Not listed
Published
August 26, 2025
Last Modified
June 23, 2026
Advisory Details (2)
Auto-updated Jun 23, 2026picklescan - Remote Code Execution via idlelib.autocomplete.AutoComplete.get_entity | Advisories | VulnCheck
https://www.vulncheck.com/advisories/picklescan-remote-code-execution-via-idlelib-autocomplete-autocomplete-get-entityMissing detection when calling built-in python idlelib.autocomplete.AutoComplete.get_entity · Advisory · mmaitre314/picklescan · GitHub
https://github.com/mmaitre314/picklescan/security/advisories/GHSA-6w4w-5w54-rjvrVendor Advisories for CVE-2025-71358(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| picklescan | 0.0.1 ... 0.0.9 (28 versions) | 0.0.29 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 44× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 03:03 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 17:52 UTCOSV refresh
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
Show 22 moreShow fewer
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 14:04 UTCEPSS rescore
- 2026-06-23 21:32 UTCEPSS rescore
- 2026-06-23 00:05 UTCEG score recompute▲ 8.10
- 2026-06-23 00:00 UTCMITRE cvelistV5CVSS v3 → 8.1 · CVSS v4 → 7.6 · severity → HIGH
- 2026-06-22 22:37 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
- CVE-2017-20208EG 9.8CRITICAL
- CVE-2017-20207EG 9.8CRITICAL
- CVE-2017-20206EG 9.8CRITICAL
- CVE-2017-20189EG 9.8CRITICAL
- CVE-2017-10992EG 9.8EPSS 95%CRITICAL
- CVE-2013-4521EG 9.8EPSS 90%CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS 98%CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-18605EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2025-71358?
When was CVE-2025-71358 disclosed?
Is CVE-2025-71358 actively exploited?
What is the CVSS score of CVE-2025-71358?
How do I remediate CVE-2025-71358?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71358
Is Your Infrastructure Affected by CVE-2025-71358?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.