CVE-2025-71349

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH 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 trace.Trace.run function when analyzing pickle files, allowing attackers to embed undetected malicious code. Remote attackers can craft malicious pickle files using trace.Trace.run in the reduce method to achieve arbitrary code execution when pickle.load processes the file.

CVSS v3
8.1
EG Score
8.1(high)
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
43%
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 Undetected trace.Trace.run in Pickle Files | Advisories | VulnCheck

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

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

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-5qwp-399c-mjwf

Vendor Advisories for CVE-2025-71349(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 15× in last 7d / 76× 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-27 01:58 UTCEG score recompute
  2. 2026-07-27 01:58 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 13:49 UTCEG score recompute
  6. 2026-07-26 13:49 UTCGHSA enrichment
  7. 2026-07-25 14:17 UTCEPSS rescore
  8. 2026-07-25 14:17 UTCEPSS rescore
  9. 2026-07-24 14:17 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 03:03 UTCEG score recompute
  13. 2026-07-22 14:08 UTCEPSS rescore
  14. 2026-07-21 15:24 UTCEPSS rescore
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-19 14:30 UTCEPSS rescore
  17. 2026-07-19 14:30 UTCEPSS rescore
  18. 2026-07-19 02:28 UTCEPSS rescore
  19. 2026-07-19 02:28 UTCEPSS rescore
  20. 2026-07-18 10:04 UTCEPSS rescore
  21. 2026-07-18 10:04 UTCEPSS rescore
  22. 2026-07-17 01:35 UTCGHSA enrichment
  23. 2026-07-16 17:02 UTCEPSS rescore
  24. 2026-07-16 17:02 UTCEPSS rescore
  25. 2026-07-16 13:30 UTCGHSA enrichment
Show 51 more
  1. 2026-07-16 01:26 UTCGHSA enrichment
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 13:23 UTCGHSA enrichment
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 01:59 UTCEPSS rescore
  7. 2026-07-15 01:18 UTCGHSA enrichment
  8. 2026-07-14 13:15 UTCGHSA enrichment
  9. 2026-07-14 01:10 UTCGHSA enrichment
  10. 2026-07-13 13:06 UTCGHSA enrichment
  11. 2026-07-13 06:12 UTCEPSS rescore
  12. 2026-07-13 01:02 UTCGHSA enrichment
  13. 2026-07-12 12:59 UTCGHSA enrichment
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 00:56 UTCGHSA enrichment
  17. 2026-07-11 12:53 UTCGHSA enrichment
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-11 00:50 UTCGHSA enrichment
  21. 2026-07-10 12:47 UTCGHSA enrichment
  22. 2026-07-10 00:43 UTCGHSA enrichment
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 12:39 UTCGHSA enrichment
  25. 2026-07-09 00:36 UTCGHSA enrichment
  26. 2026-07-08 15:15 UTCEPSS rescore
  27. 2026-07-08 12:32 UTCGHSA enrichment
  28. 2026-07-08 00:28 UTCGHSA enrichment
  29. 2026-07-07 13:46 UTCEPSS rescore
  30. 2026-07-07 12:25 UTCGHSA enrichment
  31. 2026-07-07 00:14 UTCGHSA enrichment
  32. 2026-07-06 16:27 UTCEPSS rescore
  33. 2026-07-06 12:10 UTCGHSA enrichment
  34. 2026-07-06 02:23 UTCEPSS rescore
  35. 2026-07-06 00:03 UTCGHSA enrichment
  36. 2026-07-05 11:59 UTCGHSA enrichment
  37. 2026-07-05 02:30 UTCEPSS rescore
  38. 2026-07-05 02:30 UTCEPSS rescore
  39. 2026-07-04 23:55 UTCGHSA enrichment
  40. 2026-07-04 11:52 UTCGHSA enrichment
  41. 2026-07-04 06:31 UTCEPSS rescore
  42. 2026-07-04 06:31 UTCEPSS rescore
  43. 2026-07-03 23:49 UTCGHSA enrichment
  44. 2026-07-03 11:46 UTCGHSA enrichment
  45. 2026-07-02 23:40 UTCGHSA enrichment
  46. 2026-07-02 11:37 UTCGHSA enrichment
  47. 2026-07-01 23:31 UTCGHSA enrichment
  48. 2026-07-01 15:06 UTCEPSS rescore
  49. 2026-07-01 11:28 UTCGHSA enrichment
  50. 2026-06-30 23:24 UTCEG score recompute
  51. 2026-06-30 23:23 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-71349?
CVE-2025-71349 is a high vulnerability published on June 30, 2026. picklescan before 0.0.29 fails to detect the built-in trace.Trace.run function when analyzing pickle files, allowing attackers to embed undetected malicious code. Remote attackers can craft malicious pickle files using trace.Trace.run in the reduce method to achieve arbitrary code execution when…
When was CVE-2025-71349 disclosed?
CVE-2025-71349 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-71349 actively exploited?
CVE-2025-71349 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 56.6% of all scored CVEs.
What is the CVSS score of CVE-2025-71349?
CVE-2025-71349 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-71349?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71349, 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-71349

Explore →

Is Your Infrastructure Affected by CVE-2025-71349?

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

Start Free Scan →Browse All CVEs