CVE-2025-71351

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.6% (46th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS
Elevated

Also known asEUVD-2025-210292 (ENISA EUVD) · GHSA-fh2f-24rh-r2vq (GitHub Security Advisories) · GHSA-v7x6-rv5q-mhwc (GitHub Security Advisories) · PYSEC-2026-4135 (OSV.dev)Source: ENISA EUVD

7.6EG
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.6%CVSS: 7.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

picklescan before 0.0.25 fails to detect malicious pickle files that use timeit.timeit() in the __reduce__ method, allowing remote code execution. Attackers can craft pickle files that import dangerous libraries like os and execute arbitrary system commands, which evade picklescan detection and execute when pickle.load() is called.

CVSS
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
50
EG Risk 50/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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.6%
EPSS %ILE
46th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.the CNA's CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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 21, 2026

Last Modified

November 8, 2026

Advisory Details (2)

Auto-updated Jun 22, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Missing detection when calling built-in python library function timeit.timeit() · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-v7x6-rv5q-mhwc
Web page

picklescan - Remote Code Execution via timeit.timeit() Detection Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-remote-code-execution-via-timeit-timeit-detection-bypass

Vendor Advisories for CVE-2025-71351(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pippicklescan @ 0.0.25 (fixes < 0.0.25)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
picklescan0.0.1 ... 0.0.9 (24 versions)
  • every version up to 0.0.25: fixed in 0.0.25
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 298 rows on record for this CVE, as 99 entries (1 repeat merged).

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 198 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-71351?
CVE-2025-71351 is a high-severity vulnerability; its CVE record was published on June 21, 2026. picklescan before 0.0.25 fails to detect malicious pickle files that use timeit.timeit() in the reduce method, allowing remote code execution. Attackers can craft pickle files that import dangerous libraries like os and execute arbitrary system commands, which evade picklescan detection and execute…
When was CVE-2025-71351 made public?
CVE-2025-71351 was made public on April 6, 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 21, 2026. EchelonGraph's copy of the record carries a last-modified date of November 8, 2026; the record at its source may have been updated since.
Is CVE-2025-71351 actively exploited?
CVE-2025-71351 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-71351?
CVE-2025-71351 has a CVSS base score of 7.6 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2025-71351?
A fix for CVE-2025-71351 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-71351 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-71351

Explore →

Is Your Infrastructure Affected by CVE-2025-71351?

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