picklescan before 0.0.28 fails to detect malicious pickle files that exploit torch._dynamo.guards.GuardBuilder.get function in reduce methods. Attackers can craft pickle files with embedded code that evades picklescan detection and executes arbitrary commands when loaded.
CVE-2025-71353
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-04. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- 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(high)
- 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: Routine — remediate on your standard cadence. - EPSS
- 22.2%
- KEV
- Not listed
Published
July 4, 2026
Last Modified
July 6, 2026
Advisory Details (2)
Auto-updated Jul 4, 2026picklescan - Remote Code Execution via torch._dynamo.guards.GuardBuilder.get | Advisories | VulnCheck
https://www.vulncheck.com/advisories/picklescan-remote-code-execution-via-torch-dynamo-guards-guardbuilder-getMissing detection when calling pytorch function torch._dynamo.guards.GuardBuilder.get · Advisory · mmaitre314/picklescan · GitHub
https://github.com/mmaitre314/picklescan/security/advisories/GHSA-86cj-95qr-2p4fVendor Advisories for CVE-2025-71353(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 (27 versions) | 0.0.28 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 54× 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-17 00:21 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 11:25 UTCGHSA enrichment
- 2026-07-15 22:29 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 09:33 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-14 20:35 UTCGHSA enrichment
- 2026-07-14 07:35 UTCGHSA enrichment
- 2026-07-13 18:38 UTCGHSA enrichment
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-13 05:42 UTCGHSA enrichment
Show 29 moreShow fewer
- 2026-07-12 16:46 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 03:49 UTCGHSA enrichment
- 2026-07-11 14:53 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 01:57 UTCGHSA enrichment
- 2026-07-10 13:01 UTCGHSA enrichment
- 2026-07-10 00:05 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 11:07 UTCGHSA enrichment
- 2026-07-08 22:11 UTCGHSA enrichment
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 09:15 UTCGHSA enrichment
- 2026-07-07 20:19 UTCGHSA enrichment
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 07:23 UTCGHSA enrichment
- 2026-07-06 18:26 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 05:29 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 16:33 UTCGHSA enrichment
- 2026-07-05 03:36 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 14:39 UTCGHSA enrichment
- 2026-07-04 01:42 UTCEG score recompute
- 2026-07-04 01:41 UTCMITRE cvelistV5first tracked
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-71353?
When was CVE-2025-71353 disclosed?
Is CVE-2025-71353 actively exploited?
What is the CVSS score of CVE-2025-71353?
How do I remediate CVE-2025-71353?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71353
Is Your Infrastructure Affected by CVE-2025-71353?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.