CVE-2025-71373

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM 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.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: Elevated riskExposed: 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(medium)
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 PROB
1%
EPSS %ILE
48%
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.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
picklescan0.0.1 ... 0.0.9 (32 versions)0.0.33—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 183 total refreshes for this CVE.

  1. 2026-08-26 14:45 UTCEPSS rescore
  2. 2026-08-26 14:29 UTCEG score recompute
  3. 2026-08-26 14:29 UTCGHSA enrichment
  4. 2026-08-25 13:48 UTCEPSS rescore
  5. 2026-08-25 12:12 UTCGHSA enrichment
  6. 2026-08-24 20:51 UTCEG score recompute
  7. 2026-08-24 20:51 UTCGHSA enrichment
  8. 2026-08-24 14:16 UTCEPSS rescore
  9. 2026-08-24 06:53 UTCGHSA enrichment
  10. 2026-08-23 18:45 UTCGHSA enrichment
  11. 2026-08-23 06:37 UTCEG score recompute
  12. 2026-08-23 06:37 UTCGHSA enrichment
  13. 2026-08-23 00:18 UTCEPSS rescore
  14. 2026-08-22 18:28 UTCGHSA enrichment
  15. 2026-08-22 05:23 UTCEG score recompute
  16. 2026-08-22 05:23 UTCGHSA enrichment
  17. 2026-08-21 23:48 UTCEPSS rescore
  18. 2026-08-21 17:14 UTCGHSA enrichment
  19. 2026-08-21 04:25 UTCEG score recompute
  20. 2026-08-21 04:25 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 15:51 UTCGHSA enrichment
  23. 2026-08-20 03:39 UTCEG score recompute
  24. 2026-08-20 03:39 UTCGHSA enrichment
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 12:31 UTCGHSA enrichment
  2. 2026-08-18 23:52 UTCEG score recompute
  3. 2026-08-18 23:52 UTCGHSA enrichment
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-18 11:41 UTCGHSA enrichment
  6. 2026-08-17 22:46 UTCEG score recompute
  7. 2026-08-17 22:46 UTCGHSA enrichment
  8. 2026-08-17 13:46 UTCEPSS rescore
  9. 2026-08-17 10:12 UTCGHSA enrichment
  10. 2026-08-16 22:04 UTCEG score recompute
  11. 2026-08-16 22:04 UTCGHSA enrichment
  12. 2026-08-16 14:55 UTCEPSS rescore
  13. 2026-08-16 09:56 UTCEG score recompute
  14. 2026-08-16 09:56 UTCGHSA enrichment
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 21:48 UTCGHSA enrichment
  17. 2026-08-15 09:40 UTCEG score recompute
  18. 2026-08-15 09:40 UTCGHSA enrichment
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 21:31 UTCGHSA enrichment
  21. 2026-08-14 09:23 UTCEG score recompute
  22. 2026-08-14 09:23 UTCGHSA enrichment
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 21:15 UTCGHSA enrichment
  25. 2026-08-13 09:05 UTCGHSA enrichment
  26. 2026-08-12 20:55 UTCEG score recompute
  27. 2026-08-12 20:55 UTCGHSA enrichment
  28. 2026-08-12 13:50 UTCEPSS rescore
  29. 2026-08-12 08:47 UTCGHSA enrichment
  30. 2026-08-11 20:39 UTCEG score recompute
  31. 2026-08-11 20:39 UTCGHSA enrichment
  32. 2026-08-11 13:42 UTCEPSS rescore
  33. 2026-08-11 08:31 UTCEG score recompute
  34. 2026-08-11 08:31 UTCGHSA enrichment
  35. 2026-08-10 23:59 UTCEPSS rescore
  36. 2026-08-10 20:23 UTCGHSA enrichment
  37. 2026-08-10 08:15 UTCGHSA enrichment
  38. 2026-08-09 20:07 UTCEG score recompute
  39. 2026-08-09 20:07 UTCGHSA enrichment
  40. 2026-08-09 13:46 UTCEPSS rescore
  41. 2026-08-09 07:59 UTCGHSA enrichment
  42. 2026-08-08 19:51 UTCEG score recompute
  43. 2026-08-08 19:51 UTCGHSA enrichment
  44. 2026-08-08 16:36 UTCEPSS rescore
  45. 2026-08-08 07:42 UTCGHSA enrichment
  46. 2026-08-07 19:34 UTCEG score recompute
  47. 2026-08-07 19:34 UTCGHSA enrichment
  48. 2026-08-07 16:27 UTCEPSS rescore
  49. 2026-08-07 07:26 UTCGHSA enrichment
  50. 2026-08-06 19:18 UTCEG score recompute
  51. 2026-08-06 19:18 UTCGHSA enrichment
  52. 2026-08-06 13:46 UTCEPSS rescore
  53. 2026-08-06 07:10 UTCEG score recompute
  54. 2026-08-06 07:10 UTCGHSA enrichment
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-05 19:02 UTCGHSA enrichment
  57. 2026-08-05 06:53 UTCGHSA enrichment
  58. 2026-08-04 16:01 UTCEG score recompute
  59. 2026-08-04 16:01 UTCGHSA enrichment
  60. 2026-08-04 10:37 UTCEPSS rescore
  61. 2026-08-04 03:53 UTCGHSA enrichment
  62. 2026-08-03 15:45 UTCEG score recompute
  63. 2026-08-03 15:45 UTCGHSA enrichment
  64. 2026-08-03 10:35 UTCEPSS rescore
  65. 2026-08-03 03:37 UTCEG score recompute
  66. 2026-08-03 03:37 UTCGHSA enrichment
  67. 2026-08-02 15:29 UTCGHSA enrichment
  68. 2026-08-02 03:21 UTCEG score recompute
  69. 2026-08-02 03:20 UTCGHSA enrichment
  70. 2026-08-02 02:26 UTCEPSS rescore
  71. 2026-08-01 15:12 UTCEG score recompute
  72. 2026-08-01 15:12 UTCGHSA enrichment
  73. 2026-08-01 04:15 UTCEPSS rescore
  74. 2026-08-01 03:03 UTCGHSA enrichment
  75. 2026-07-31 14:52 UTCGHSA enrichment

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 1% probability of exploitation in the next 30 days, which ranks it in the top 52.1% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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