CVE-2025-71359

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
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: Elevated riskExposed: 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 malicious pickle payloads that utilize lib2to3.pgen2.grammar.Grammar.loads in the reduce method, allowing remote code execution. Attackers can craft pickle files embedding dangerous code that evades picklescan detection and executes during pickle.load() deserialization.

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 computed
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

July 4, 2026

Last Modified

July 6, 2026

Advisory Details (2)

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

picklescan - Unsafe Deserialization via lib2to3.pgen2.grammar.Grammar.loads | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-unsafe-deserialization-via-lib2to3-pgen2-grammar-grammar-loads
github Patch Available🟡 PoC Available

Missing detection when calling built-in python lib2to3.pgen2.grammar.Grammar.loads · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-f54q-57x4-jg88

Vendor Advisories for CVE-2025-71359(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 16× 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.

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

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

Frequently asked(5)

What is CVE-2025-71359?
CVE-2025-71359 is a high vulnerability published on July 4, 2026. picklescan before 0.0.29 fails to detect malicious pickle payloads that utilize lib2to3.pgen2.grammar.Grammar.loads in the reduce method, allowing remote code execution. Attackers can craft pickle files embedding dangerous code that evades picklescan detection and executes during pickle.load()…
When was CVE-2025-71359 disclosed?
CVE-2025-71359 was first published in the National Vulnerability Database on July 4, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71359 actively exploited?
CVE-2025-71359 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-71359?
CVE-2025-71359 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-71359?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71359, 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-71359

Explore →

Is Your Infrastructure Affected by CVE-2025-71359?

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

Start Free Scan →Browse All CVEs