CVE-2025-71375

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH 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.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

picklescan before 0.0.34 fails to detect the _operator.methodcaller built-in function when scanning pickle files for malicious code. Attackers can craft malicious pickle payloads using _operator.methodcaller that evade detection and execute arbitrary code when loaded by pickle.load().

CVSS v3
8.1
EG Score
8.1(high)
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
29.0%
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 - Undetected Remote Code Execution via _operator.methodcaller | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-undetected-remote-code-execution-via-operator-methodcaller
github Patch Available🟡 PoC Available

Missing detection when calling built-in python _operator.methodcaller · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-955r-x9j8-7rhh

Vendor Advisories for CVE-2025-71375(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 (33 versions)0.0.34—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 54× 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.

  1. 2026-07-23 03:03 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-19 02:28 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 18:18 UTCGHSA enrichment
  12. 2026-07-16 17:02 UTCEPSS rescore
  13. 2026-07-16 17:02 UTCEPSS rescore
  14. 2026-07-16 05:36 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:55 UTCGHSA enrichment
  18. 2026-07-15 04:13 UTCGHSA enrichment
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-15 01:59 UTCEPSS rescore
  21. 2026-07-14 15:32 UTCGHSA enrichment
  22. 2026-07-14 02:50 UTCGHSA enrichment
  23. 2026-07-13 14:09 UTCGHSA enrichment
  24. 2026-07-13 06:12 UTCEPSS rescore
  25. 2026-07-13 01:26 UTCGHSA enrichment
Show 29 more
  1. 2026-07-12 12:45 UTCGHSA enrichment
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-12 00:03 UTCGHSA enrichment
  5. 2026-07-11 11:22 UTCGHSA enrichment
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-10 22:40 UTCGHSA enrichment
  9. 2026-07-10 09:59 UTCGHSA enrichment
  10. 2026-07-09 21:18 UTCGHSA enrichment
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 08:37 UTCGHSA enrichment
  13. 2026-07-08 19:56 UTCGHSA enrichment
  14. 2026-07-08 15:15 UTCEPSS rescore
  15. 2026-07-08 07:15 UTCGHSA enrichment
  16. 2026-07-07 18:31 UTCGHSA enrichment
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 05:50 UTCGHSA enrichment
  19. 2026-07-06 17:09 UTCGHSA enrichment
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 04:28 UTCGHSA enrichment
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-05 15:47 UTCGHSA enrichment
  24. 2026-07-05 03:06 UTCGHSA enrichment
  25. 2026-07-05 02:30 UTCEPSS rescore
  26. 2026-07-05 02:30 UTCEPSS rescore
  27. 2026-07-04 14:24 UTCGHSA enrichment
  28. 2026-07-04 01:42 UTCEG score recompute
  29. 2026-07-04 01:41 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-71375?
CVE-2025-71375 is a high vulnerability published on July 4, 2026. picklescan before 0.0.34 fails to detect the operator.methodcaller built-in function when scanning pickle files for malicious code. Attackers can craft malicious pickle payloads using operator.methodcaller that evade detection and execute arbitrary code when loaded by pickle.load().
When was CVE-2025-71375 disclosed?
CVE-2025-71375 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-71375 actively exploited?
CVE-2025-71375 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-71375?
CVE-2025-71375 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-71375?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71375, 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-71375

Explore →

Is Your Infrastructure Affected by CVE-2025-71375?

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

Start Free Scan →Browse All CVEs