CVE-2025-71373

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 — 4 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.33 fails to detect operator.methodcaller function calls in pickle files, allowing attackers to bypass security checks. Remote attackers can craft malicious pickle payloads using operator.methodcaller that execute arbitrary code when loaded, compromising systems relying on picklescan for validation.

CVSS v3
8.1
EG Score
8.1(high)
EPSS
35.6%
KEV
Not listed

Published

July 4, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jul 4, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

picklescan - Remote Code Execution via operator.methodcaller Detection Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-remote-code-execution-via-operator-methodcaller-detection-bypass
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-x843-g5mx-g377

Vendor Advisories for CVE-2025-71373(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 18× 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-07 02:34 UTCEG score recompute
  2. 2026-07-07 02:34 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 14:26 UTCEG score recompute
  5. 2026-07-06 14:26 UTCGHSA enrichment
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:16 UTCEG score recompute
  8. 2026-07-06 02:16 UTCGHSA enrichment
  9. 2026-07-05 14:07 UTCEG score recompute
  10. 2026-07-05 14:07 UTCGHSA enrichment
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-05 01:58 UTCEG score recompute
  14. 2026-07-05 01:58 UTCGHSA enrichment
  15. 2026-07-04 13:50 UTCEG score recompute
  16. 2026-07-04 13:50 UTCGHSA enrichment
  17. 2026-07-04 01:42 UTCEG score recompute
  18. 2026-07-04 01:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2025-71373?
CVE-2025-71373 is a high vulnerability published on July 4, 2026. picklescan before 0.0.33 fails to detect operator.methodcaller function calls in pickle files, allowing attackers to bypass security checks. Remote attackers can craft malicious pickle payloads using operator.methodcaller that execute arbitrary code when loaded, compromising systems relying on…
When was CVE-2025-71373 disclosed?
CVE-2025-71373 was first published in the National Vulnerability Database on July 4, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71373 actively exploited?
CVE-2025-71373 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-71373?
CVE-2025-71373 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2025-71373?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71373, 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

Explore the affected products and dependency analysis for CVE-2025-71373

Explore →

Is Your Infrastructure Affected by CVE-2025-71373?

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

Start Free Scan →Browse All CVEs