CVE-2025-71372

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.33 fails to detect the numpy.f2py.crackfortran.getlincoef gadget in pickle __reduce__ methods, allowing arbitrary code execution. Attackers can craft malicious pickle files that execute arbitrary Python code when loaded, bypassing Picklescan's safety checks and enabling supply-chain poisoning of shared model files.

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
45%
KEV
Not listed

Published

July 4, 2026

Last Modified

July 7, 2026

Advisory Details (2)

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

Picklescan - Arbitrary Code Execution via numpy.f2py.crackfortran.getlincoef Gadget | Advisories | VulnCheck

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

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

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-rrxm-2pvv-m66x

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

Frequently asked(5)

What is CVE-2025-71372?
CVE-2025-71372 is a high vulnerability published on July 4, 2026. Picklescan before 0.0.33 fails to detect the numpy.f2py.crackfortran.getlincoef gadget in pickle reduce methods, allowing arbitrary code execution. Attackers can craft malicious pickle files that execute arbitrary Python code when loaded, bypassing Picklescan's safety checks and enabling…
When was CVE-2025-71372 disclosed?
CVE-2025-71372 was first published in the National Vulnerability Database on July 4, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71372 actively exploited?
CVE-2025-71372 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 55.5% of all scored CVEs.
What is the CVSS score of CVE-2025-71372?
CVE-2025-71372 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-71372?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71372, 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-71372

Explore →

Is Your Infrastructure Affected by CVE-2025-71372?

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

Start Free Scan →Browse All CVEs