CVE-2026-53875

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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

picklescan before 1.0.3 contains a scanning bypass vulnerability in the scan_pytorch function that allows attackers to embed malicious magic numbers via dynamic eval using the __reduce__ trick. Attackers can craft malicious PyTorch payloads that evade picklescan detection while remaining executable, enabling arbitrary code execution when loaded with torch.load().

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
35.0%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jun 17, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Picklescan (scan_pytorch) Bypass via dynamic eval MAGIC_NUMBER · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-97f8-7cmv-76j2
generic

picklescan - Scanning Bypass via Dynamic Eval in scan_pytorch | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-scanning-bypass-via-dynamic-eval-in-scan-pytorch
github_commit Patch Available

commit 2a8383cfeb41 (mmaitre314/picklescan)

Patch available: mmaitre314/picklescan v0.0.26 (contains commit 2a8383cfeb41)

https://github.com/mmaitre314/picklescan/commit/2a8383cfeb4158567f9770d86597300c9e508d0f

Vendor Advisories for CVE-2026-53875(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 ... 1.0.2 (38 versions)1.0.3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 84× 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-11 08:27 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:05 UTCEG score recompute
  4. 2026-07-10 19:07 UTCEG score recompute
  5. 2026-07-10 06:05 UTCEG score recompute
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 17:04 UTCEG score recompute
  9. 2026-07-09 02:21 UTCEG score recompute
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 13:15 UTCEG score recompute
  13. 2026-07-08 00:16 UTCEG score recompute
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 11:17 UTCEG score recompute
  17. 2026-07-06 21:48 UTCEG score recompute
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 06:28 UTCEG score recompute
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-05 17:21 UTCEG score recompute
  24. 2026-07-05 04:23 UTCEG score recompute
  25. 2026-07-05 02:31 UTCEPSS rescore
Show 59 more
  1. 2026-07-05 02:30 UTCEPSS rescore
  2. 2026-07-04 15:07 UTCEG score recompute
  3. 2026-07-04 06:31 UTCEPSS rescore
  4. 2026-07-04 06:31 UTCEPSS rescore
  5. 2026-07-04 02:09 UTCEG score recompute
  6. 2026-07-03 13:05 UTCEG score recompute
  7. 2026-07-02 23:16 UTCEG score recompute
  8. 2026-07-02 10:17 UTCEG score recompute
  9. 2026-07-01 21:19 UTCEG score recompute
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 08:21 UTCEG score recompute
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 19:23 UTCEG score recompute
  14. 2026-06-30 06:25 UTCEG score recompute
  15. 2026-06-29 17:26 UTCEG score recompute
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 04:27 UTCEG score recompute
  19. 2026-06-28 15:26 UTCEG score recompute
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 02:28 UTCEG score recompute
  24. 2026-06-27 13:29 UTCEG score recompute
  25. 2026-06-27 03:08 UTCEPSS rescore
  26. 2026-06-27 00:30 UTCEG score recompute
  27. 2026-06-26 11:30 UTCEG score recompute
  28. 2026-06-25 21:28 UTCEG score recompute
  29. 2026-06-25 13:49 UTCEPSS rescore
  30. 2026-06-25 08:29 UTCEG score recompute
  31. 2026-06-24 19:31 UTCEG score recompute
  32. 2026-06-24 14:05 UTCEPSS rescore
  33. 2026-06-24 06:04 UTCEG score recompute
  34. 2026-06-23 21:33 UTCEPSS rescore
  35. 2026-06-23 21:33 UTCEPSS rescore
  36. 2026-06-23 17:01 UTCEG score recompute
  37. 2026-06-23 04:00 UTCEG score recompute
  38. 2026-06-22 14:57 UTCEG score recompute
  39. 2026-06-22 14:25 UTCEPSS rescore
  40. 2026-06-22 14:25 UTCEPSS rescore
  41. 2026-06-22 01:57 UTCEG score recompute
  42. 2026-06-21 14:56 UTCEPSS rescore
  43. 2026-06-21 14:56 UTCEPSS rescore
  44. 2026-06-21 12:58 UTCEG score recompute
  45. 2026-06-21 01:59 UTCEPSS rescore
  46. 2026-06-21 01:59 UTCEPSS rescore
  47. 2026-06-20 23:56 UTCEG score recompute
  48. 2026-06-20 10:52 UTCEG score recompute
  49. 2026-06-19 21:53 UTCEG score recompute
  50. 2026-06-19 19:26 UTCEPSS rescore
  51. 2026-06-19 19:26 UTCEPSS rescore
  52. 2026-06-19 08:54 UTCEG score recompute
  53. 2026-06-18 19:54 UTCEG score recompute
  54. 2026-06-18 17:52 UTCEPSS rescore
  55. 2026-06-18 17:52 UTCEPSS rescore
  56. 2026-06-18 06:53 UTCEG score recompute
  57. 2026-06-18 06:53 UTCGHSA enrichment
  58. 2026-06-17 17:52 UTCEG score recompute
  59. 2026-06-17 17:52 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53875?
CVE-2026-53875 is a high vulnerability published on June 17, 2026. picklescan before 1.0.3 contains a scanning bypass vulnerability in the scan_pytorch function that allows attackers to embed malicious magic numbers via dynamic eval using the reduce trick. Attackers can craft malicious PyTorch payloads that evade picklescan detection while remaining executable,…
When was CVE-2026-53875 disclosed?
CVE-2026-53875 was first published in the National Vulnerability Database on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53875 actively exploited?
CVE-2026-53875 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53875?
CVE-2026-53875 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-53875?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53875, 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-2026-53875

Explore →

Is Your Infrastructure Affected by CVE-2026-53875?

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

Start Free Scan →Browse All CVEs