CVE-2025-71378

HIGHNVD 7.88.1▲
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-21. NVD baseline CVSS 7.8; sources differ by 0.3.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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.30 fails to detect cProfile.runctx function calls in pickle file reduce methods, allowing attackers to execute arbitrary code. Malicious pickle files bypass picklescan detection and execute remote code when loaded via pickle.load().

CVSS v3
7.8
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
0%
EPSS %ILE
41%
KEV
Not listed

Published

June 21, 2026

Last Modified

June 26, 2026

Advisory Details (2)

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

picklescan - Remote Code Execution via Undetected cProfile.runctx in Pickle Files | Advisories | VulnCheck

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

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

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-9w88-8rmg-7g2p

Vendor Advisories for CVE-2025-71378(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 (29 versions)0.0.30—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 42× 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 237 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-71378?
CVE-2025-71378 is a high vulnerability published on June 21, 2026. picklescan before 0.0.30 fails to detect cProfile.runctx function calls in pickle file reduce methods, allowing attackers to execute arbitrary code. Malicious pickle files bypass picklescan detection and execute remote code when loaded via pickle.load().
When was CVE-2025-71378 disclosed?
CVE-2025-71378 was first published in the National Vulnerability Database on June 21, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71378 actively exploited?
CVE-2025-71378 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.5% of all scored CVEs.
What is the CVSS score of CVE-2025-71378?
CVE-2025-71378 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.1.
How do I remediate CVE-2025-71378?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71378, 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-71378

Explore →

Is Your Infrastructure Affected by CVE-2025-71378?

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

Start Free Scan →Browse All CVEs