CVE-2025-71374

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-01. 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 week
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

picklescan before 0.0.29 fails to detect the built-in python profile.Profile.run function when used in pickle reduce methods, allowing attackers to execute arbitrary code. Remote attackers can craft malicious pickle files that bypass picklescan detection and achieve code execution upon deserialization.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 30, 2026

Last Modified

October 5, 2026

Advisory Details (2)

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

picklescan - Arbitrary Code Execution via Undetected profile.Profile.run | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-arbitrary-code-execution-via-undetected-profile-profile-run
GitHub advisoryMentions a patch (unverified)

Missing detection when calling built-in python profile.Profile.run · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-x696-vm39-cp64

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-71374?
CVE-2025-71374 is a high-severity vulnerability; its CVE record was published on June 30, 2026. picklescan before 0.0.29 fails to detect the built-in python profile.Profile.run function when used in pickle reduce methods, allowing attackers to execute arbitrary code. Remote attackers can craft malicious pickle files that bypass picklescan detection and achieve code execution upon…
When was CVE-2025-71374 made public?
CVE-2025-71374 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 June 30, 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-71374 actively exploited?
CVE-2025-71374 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-71374?
CVE-2025-71374 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-71374?
A fix for CVE-2025-71374 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-71374 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-71374

Explore →

Is Your Infrastructure Affected by CVE-2025-71374?

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

Book a Demo →Browse All CVEs