CVE-2025-71365

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-23. 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: 0%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.33 fails to detect malicious pickle files that invoke numpy.f2py.crackfortran.myeval function through the reduce method. Attackers can craft malicious pickle files embedding arbitrary code that evades picklescan detection and executes remote code when loaded.

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
0%
EPSS %ILE
36%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 23, 2026

Advisory Details (2)

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

picklescan - Arbitrary Code Execution via numpy.f2py.crackfortran.myeval Detection Bypass | Advisories | VulnCheck

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

Missing detection when calling numpy function numpy.f2py.crackfortran.myeval · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-3329-ghmp-jmv5

Vendor Advisories for CVE-2025-71365(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 (32 versions)0.0.33—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 98× 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 203 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-71365?
CVE-2025-71365 is a high vulnerability published on June 23, 2026. picklescan before 0.0.33 fails to detect malicious pickle files that invoke numpy.f2py.crackfortran.myeval function through the reduce method. Attackers can craft malicious pickle files embedding arbitrary code that evades picklescan detection and executes remote code when loaded.
When was CVE-2025-71365 disclosed?
CVE-2025-71365 was first published in the National Vulnerability Database on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71365 actively exploited?
CVE-2025-71365 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 64.1% of all scored CVEs.
What is the CVSS score of CVE-2025-71365?
CVE-2025-71365 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-71365?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71365, 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-71365

Explore →

Is Your Infrastructure Affected by CVE-2025-71365?

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

Start Free Scan →Browse All CVEs