CVE-2025-71365

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Elevated
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

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 (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 23, 2026

Last Modified

October 5, 2026

Advisory Details (2)

Auto-updated Jun 23, 2026
Patch available. Sources: github.
Web page

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 advisoryMentions a patch (unverified)

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 rangeFix by version rangeDependents
picklescan0.0.1 ... 0.0.9 (32 versions)
  • every version up to 0.0.33: fixed in 0.0.33
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 251 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 152 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-71365?
CVE-2025-71365 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2025-71365 was made public on December 27, 2025: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 23, 2026. EchelonGraph's copy of the record carries a last-modified date of October 5, 2026; the record at its source may have been updated since.
Is CVE-2025-71365 actively exploited?
CVE-2025-71365 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-71365?
CVE-2025-71365 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-71365?
A fix for CVE-2025-71365 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-71365 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs