CVE-2025-71352

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

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

picklescan before 0.0.29 fails to detect the built-in Python trace.Trace.runctx function when used in pickle file reduce methods, allowing attackers to execute arbitrary code. Remote attackers can craft malicious pickle files with trace.Trace.runctx payloads that bypass picklescan detection and execute code upon pickle.load() invocation.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
41(Track)
EG Risk 41/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 computed
Severity81% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
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 - Remote Code Execution via Undetected trace.Trace.runctx in Pickle Files | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-remote-code-execution-via-undetected-trace-trace-runctx-in-pickle-files
github Patch Available🟡 PoC Available

Missing detection when calling built-in python trace.Trace.runctx · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-g344-hcph-8vgg

Vendor Advisories for CVE-2025-71352(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 (28 versions)0.0.29—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 183 total refreshes for this CVE.

  1. 2026-08-26 14:45 UTCEPSS rescore
  2. 2026-08-25 13:48 UTCEPSS rescore
  3. 2026-08-25 01:29 UTCEG score recompute
  4. 2026-08-25 01:29 UTCGHSA enrichment
  5. 2026-08-24 14:16 UTCEPSS rescore
  6. 2026-08-24 12:38 UTCEG score recompute
  7. 2026-08-24 12:38 UTCGHSA enrichment
  8. 2026-08-23 23:27 UTCGHSA enrichment
  9. 2026-08-23 10:36 UTCEG score recompute
  10. 2026-08-23 10:36 UTCGHSA enrichment
  11. 2026-08-23 00:18 UTCEPSS rescore
  12. 2026-08-22 21:46 UTCGHSA enrichment
  13. 2026-08-22 08:53 UTCEG score recompute
  14. 2026-08-22 08:53 UTCGHSA enrichment
  15. 2026-08-21 23:48 UTCEPSS rescore
  16. 2026-08-21 20:02 UTCGHSA enrichment
  17. 2026-08-21 07:11 UTCEG score recompute
  18. 2026-08-21 07:11 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 18:14 UTCGHSA enrichment
  21. 2026-08-20 05:23 UTCEG score recompute
  22. 2026-08-20 05:23 UTCGHSA enrichment
  23. 2026-08-19 17:03 UTCEPSS rescore
  24. 2026-08-19 12:33 UTCGHSA enrichment
  25. 2026-08-18 22:59 UTCEG score recompute
Show 75 more
  1. 2026-08-18 22:59 UTCGHSA enrichment
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-18 05:01 UTCEG score recompute
  4. 2026-08-18 05:01 UTCGHSA enrichment
  5. 2026-08-17 13:46 UTCEPSS rescore
  6. 2026-08-17 12:26 UTCGHSA enrichment
  7. 2026-08-16 23:13 UTCEG score recompute
  8. 2026-08-16 23:13 UTCGHSA enrichment
  9. 2026-08-16 14:55 UTCEPSS rescore
  10. 2026-08-16 10:23 UTCEG score recompute
  11. 2026-08-16 10:23 UTCGHSA enrichment
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 21:33 UTCGHSA enrichment
  14. 2026-08-15 08:43 UTCEG score recompute
  15. 2026-08-15 08:43 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 19:52 UTCGHSA enrichment
  18. 2026-08-14 07:02 UTCEG score recompute
  19. 2026-08-14 07:02 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 18:11 UTCGHSA enrichment
  22. 2026-08-13 04:30 UTCGHSA enrichment
  23. 2026-08-12 15:40 UTCEG score recompute
  24. 2026-08-12 15:40 UTCGHSA enrichment
  25. 2026-08-12 13:50 UTCEPSS rescore
  26. 2026-08-12 02:39 UTCGHSA enrichment
  27. 2026-08-11 13:49 UTCEG score recompute
  28. 2026-08-11 13:49 UTCGHSA enrichment
  29. 2026-08-11 13:42 UTCEPSS rescore
  30. 2026-08-11 00:59 UTCEG score recompute
  31. 2026-08-11 00:59 UTCGHSA enrichment
  32. 2026-08-10 23:59 UTCEPSS rescore
  33. 2026-08-10 12:09 UTCGHSA enrichment
  34. 2026-08-09 23:19 UTCEG score recompute
  35. 2026-08-09 23:19 UTCGHSA enrichment
  36. 2026-08-09 13:46 UTCEPSS rescore
  37. 2026-08-09 10:29 UTCGHSA enrichment
  38. 2026-08-08 21:39 UTCEG score recompute
  39. 2026-08-08 21:39 UTCGHSA enrichment
  40. 2026-08-08 16:36 UTCEPSS rescore
  41. 2026-08-08 08:48 UTCGHSA enrichment
  42. 2026-08-07 19:58 UTCEG score recompute
  43. 2026-08-07 19:58 UTCGHSA enrichment
  44. 2026-08-07 16:27 UTCEPSS rescore
  45. 2026-08-07 07:08 UTCGHSA enrichment
  46. 2026-08-06 18:18 UTCEG score recompute
  47. 2026-08-06 18:18 UTCGHSA enrichment
  48. 2026-08-06 13:46 UTCEPSS rescore
  49. 2026-08-06 05:27 UTCEG score recompute
  50. 2026-08-06 05:27 UTCGHSA enrichment
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-05 16:37 UTCGHSA enrichment
  53. 2026-08-04 22:05 UTCEG score recompute
  54. 2026-08-04 22:05 UTCGHSA enrichment
  55. 2026-08-04 10:37 UTCEPSS rescore
  56. 2026-08-04 08:44 UTCGHSA enrichment
  57. 2026-08-03 19:49 UTCEG score recompute
  58. 2026-08-03 19:49 UTCGHSA enrichment
  59. 2026-08-03 10:35 UTCEPSS rescore
  60. 2026-08-03 06:59 UTCGHSA enrichment
  61. 2026-08-02 16:37 UTCGHSA enrichment
  62. 2026-08-02 03:46 UTCEG score recompute
  63. 2026-08-02 03:46 UTCGHSA enrichment
  64. 2026-08-02 02:26 UTCEPSS rescore
  65. 2026-08-01 14:56 UTCEG score recompute
  66. 2026-08-01 14:56 UTCGHSA enrichment
  67. 2026-08-01 04:15 UTCEPSS rescore
  68. 2026-08-01 02:05 UTCGHSA enrichment
  69. 2026-07-31 12:54 UTCEG score recompute
  70. 2026-07-31 12:54 UTCGHSA enrichment
  71. 2026-07-31 00:02 UTCEG score recompute
  72. 2026-07-31 00:01 UTCGHSA enrichment
  73. 2026-07-30 16:27 UTCEPSS rescore
  74. 2026-07-30 11:11 UTCEG score recompute
  75. 2026-07-30 11:11 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2025-71352?
CVE-2025-71352 is a high vulnerability published on June 30, 2026. picklescan before 0.0.29 fails to detect the built-in Python trace.Trace.runctx function when used in pickle file reduce methods, allowing attackers to execute arbitrary code. Remote attackers can craft malicious pickle files with trace.Trace.runctx payloads that bypass picklescan detection and…
When was CVE-2025-71352 disclosed?
CVE-2025-71352 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-71352 actively exploited?
CVE-2025-71352 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.1% of all scored CVEs.
What is the CVSS score of CVE-2025-71352?
CVE-2025-71352 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-71352?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71352, 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-71352

Explore →

Is Your Infrastructure Affected by CVE-2025-71352?

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

Start Free Scan →Browse All CVEs