CVE-2025-71355

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 58% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Picklescan before 0.0.25 fails to detect unsafe global functions in the Numpy library, allowing attackers to bypass static analysis and execute arbitrary code during deserialization. Attackers can craft malicious pickle files using numpy.testing._private.utils.runstring within the reduce method to import dangerous libraries like os and execute arbitrary OS commands when the pickle file is loaded.

CVSS v3
7.6
EG Score
7.6(medium)
EG Risk
EPSS
42.8%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 1, 2026

Advisory Details (2)

Auto-updated Jul 1, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Picklescan - Arbitrary Code Execution via Unsafe Numpy Function Detection Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-arbitrary-code-execution-via-unsafe-numpy-function-detection-bypass
github Patch Available🟡 PoC Available

Picklescan failed to detect to some unsafe global function in Numpy library · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-fj43-3qmq-673f

Vendor Advisories for CVE-2025-71355(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)
PackageVulnerable rangeFixed inDependents
picklescan0.0.1 ... 0.0.9 (24 versions)0.0.25

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 63× 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.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 23:51 UTCGHSA enrichment
  11. 2026-07-16 17:02 UTCEPSS rescore
  12. 2026-07-16 17:02 UTCEPSS rescore
  13. 2026-07-16 11:28 UTCGHSA enrichment
  14. 2026-07-15 23:05 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 10:41 UTCGHSA enrichment
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-15 01:59 UTCEPSS rescore
  20. 2026-07-14 22:15 UTCGHSA enrichment
  21. 2026-07-14 09:52 UTCGHSA enrichment
  22. 2026-07-13 21:27 UTCGHSA enrichment
  23. 2026-07-13 09:04 UTCGHSA enrichment
  24. 2026-07-13 06:12 UTCEPSS rescore
  25. 2026-07-12 20:40 UTCGHSA enrichment
Show 38 more
  1. 2026-07-12 08:16 UTCGHSA enrichment
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-11 19:53 UTCGHSA enrichment
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-11 07:30 UTCGHSA enrichment
  8. 2026-07-10 19:06 UTCGHSA enrichment
  9. 2026-07-10 06:42 UTCGHSA enrichment
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 18:17 UTCGHSA enrichment
  12. 2026-07-09 05:53 UTCGHSA enrichment
  13. 2026-07-08 17:29 UTCGHSA enrichment
  14. 2026-07-08 15:15 UTCEPSS rescore
  15. 2026-07-08 05:06 UTCGHSA enrichment
  16. 2026-07-07 16:41 UTCGHSA enrichment
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 04:17 UTCGHSA enrichment
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 15:53 UTCGHSA enrichment
  21. 2026-07-06 03:30 UTCGHSA enrichment
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-05 14:59 UTCGHSA enrichment
  24. 2026-07-05 02:35 UTCGHSA enrichment
  25. 2026-07-05 02:30 UTCEPSS rescore
  26. 2026-07-05 02:30 UTCEPSS rescore
  27. 2026-07-04 14:12 UTCGHSA enrichment
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-04 06:31 UTCEPSS rescore
  30. 2026-07-04 01:48 UTCGHSA enrichment
  31. 2026-07-03 13:25 UTCGHSA enrichment
  32. 2026-07-03 01:02 UTCGHSA enrichment
  33. 2026-07-02 12:38 UTCGHSA enrichment
  34. 2026-07-02 00:09 UTCGHSA enrichment
  35. 2026-07-01 15:06 UTCEPSS rescore
  36. 2026-07-01 11:47 UTCGHSA enrichment
  37. 2026-06-30 23:24 UTCEG score recompute
  38. 2026-06-30 23:23 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2025-71355?
CVE-2025-71355 is a high vulnerability published on June 30, 2026. Picklescan before 0.0.25 fails to detect unsafe global functions in the Numpy library, allowing attackers to bypass static analysis and execute arbitrary code during deserialization. Attackers can craft malicious pickle files using numpy.testing._private.utils.runstring within the reduce method to…
When was CVE-2025-71355 disclosed?
CVE-2025-71355 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71355 actively exploited?
CVE-2025-71355 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-71355?
CVE-2025-71355 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2025-71355?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71355, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71355

Explore →

Is Your Infrastructure Affected by CVE-2025-71355?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.