CVE-2025-71342

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-07-04. 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
Trending — 3 sources updated this weekElevated
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.5%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

picklescan before 0.0.30 fails to detect malicious pickle files using idlelib.run.Executive.runcode in reduce methods. Attackers can embed undetected code in pickle files that executes during pickle.load, enabling remote code execution in PyTorch models and supply chain attacks.

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.5%
EPSS %ILE
43rd
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

July 4, 2026

Last Modified

October 5, 2026

Advisory Details (2)

Auto-updated Jul 4, 2026
Patch available. Sources: github.
Web page

picklescan - Undetected Remote Code Execution via idlelib.run.Executive.runcode | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-undetected-remote-code-execution-via-idlelib-run-executive-runcode
GitHub advisoryMentions a patch (unverified)

Missing detection when calling built-in python idlelib.run.Executive.runcode · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-m869-42cg-3xwr

Vendor Advisories for CVE-2025-71342(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 (29 versions)
  • every version up to 0.0.30: fixed in 0.0.30
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 41× 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 252 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 153 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.5% · 43rd percentile
  5. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-05 16:29 UTCEG score recompute
  12. 2026-10-05 16:29 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  16. 2026-09-30 16:28 UTCEG score recompute
  17. 2026-09-30 16:28 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  24. 2026-09-23 06:33 UTCEG score recompute
  25. 2026-09-23 06:33 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
Show 74 more
  1. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-09-18 06:11 UTCEG score recompute
  3. 2026-09-18 06:11 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  5. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  6. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  7. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  8. 2026-09-14 11:44 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-09-14 00:00 UTCEG score recompute
  10. 2026-09-14 00:00 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  11. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-09-13 08:53 UTCEG score recompute
  13. 2026-09-13 08:53 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  14. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-09-12 13:53 UTCEG score recompute
  16. 2026-09-12 13:53 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-09-06 14:16 UTCEG score recompute
  23. 2026-09-06 14:16 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  24. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-09-05 23:37 UTCEG score recompute
  26. 2026-09-05 23:37 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  27. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  28. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  29. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  30. 2026-08-30 22:30 UTCEG score recompute
  31. 2026-08-30 22:30 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  32. 2026-08-30 11:16 UTCEG score recompute
  33. 2026-08-30 11:16 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  34. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  35. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  36. 2026-08-27 22:09 UTCEG score recompute
  37. 2026-08-27 22:09 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  38. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  39. 2026-08-27 02:53 UTCEG score recompute
  40. 2026-08-27 02:53 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  41. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  42. 2026-08-26 14:29 UTCEG score recompute
  43. 2026-08-26 14:29 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  44. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  45. 2026-08-25 12:12 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  46. 2026-08-24 20:51 UTCEG score recompute
  47. 2026-08-24 20:51 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  48. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  49. 2026-08-24 04:19 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  50. 2026-08-23 17:04 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  51. 2026-08-23 05:50 UTCEG score recompute
  52. 2026-08-23 05:50 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  53. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  54. 2026-08-22 18:35 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  55. 2026-08-22 05:25 UTCEG score recompute
  56. 2026-08-22 05:25 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  57. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  58. 2026-08-21 15:47 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  59. 2026-08-21 04:25 UTCEG score recompute
  60. 2026-08-21 04:25 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  61. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  62. 2026-08-20 15:51 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  63. 2026-08-20 03:39 UTCEG score recompute
  64. 2026-08-20 03:39 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  65. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  66. 2026-08-19 10:17 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  67. 2026-08-18 22:55 UTCEG score recompute
  68. 2026-08-18 22:55 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  69. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  70. 2026-08-18 11:41 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  71. 2026-08-17 22:46 UTCEG score recompute
  72. 2026-08-17 22:46 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1
  73. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  74. 2026-08-17 09:46 UTCGHSA enrichmentGHSA-j6fw-8849-4cxh · GitHub severity HIGH · GitHub CVSS 8.1

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-71342?
CVE-2025-71342 is a high-severity vulnerability; its CVE record was published on July 4, 2026. picklescan before 0.0.30 fails to detect malicious pickle files using idlelib.run.Executive.runcode in reduce methods. Attackers can embed undetected code in pickle files that executes during pickle.load, enabling remote code execution in PyTorch models and supply chain attacks.
When was CVE-2025-71342 made public?
CVE-2025-71342 was made public on August 26, 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 July 4, 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-71342 actively exploited?
CVE-2025-71342 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-71342?
CVE-2025-71342 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-71342?
A fix for CVE-2025-71342 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-71342 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-71342

Explore →

Is Your Infrastructure Affected by CVE-2025-71342?

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

Book a Demo →Browse All CVEs