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 63% 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.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.7%
EPSS %ILE
51st
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.
githubMentions a patch (unverified)🟡 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 rangeFix by version rangeDependents
picklescan0.0.1 ... 1.0.2 (38 versions)
  • every version up to 1.0.3: fixed in 1.0.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 27× 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 153 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

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 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 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53875?
CVE-2026-53875 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53875?
A fix for CVE-2026-53875 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53875 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-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.

Book a Demo →Browse All CVEs