# CVE-2026-53875 — picklescan

> As of 2026-06-17, CVE-2026-53875 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in picklescan, CVSS v4.0 7.1, EPSS 0.4% (34.5th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-53875 as of 2026-06-17; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-06-17

## What is CVE-2026-53875?

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().

The record classifies CVE-2026-53875 under weakness class [CWE-95](https://intel.threadlinqs.com/cwe/CWE-95). 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 110 days ago.

## Severity and exploitation probability

- **CVSS v4.0 base score:** 7.1 — High (derived from score) (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **EPSS (FIRST):** 0.4% probability of exploitation in the next 30 days, higher than 34.5% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-06-17

## Is CVE-2026-53875 being exploited?

It currently carries a trending score of 38 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [picklescan](https://intel.threadlinqs.com/vendors/picklescan): picklescan

## How to fix CVE-2026-53875

No vendor patch reference has been recorded for CVE-2026-53875 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-53875

No threat campaign in the Threadlinqs corpus currently references CVE-2026-53875, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on 2026-06-19. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — vendor advisory](https://github.com/mmaitre314/picklescan/security/advisories/GHSA-97f8-7cmv-76j2)
- [github.com — patch](https://github.com/mmaitre314/picklescan/commit/2a8383cfeb4158567f9770d86597300c9e508d0f)
- [github.com — patch (134179474539648ba7dee1317959529fbd0e7f89)](https://github.com/mmaitre314/picklescan/commit/134179474539648ba7dee1317959529fbd0e7f89)

**Third-party advisory**

- [vulncheck.com — third party advisory](https://www.vulncheck.com/advisories/picklescan-scanning-bypass-via-dynamic-eval-in-scan-pytorch)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-53875
Full detection coverage and IOCs for threats exploiting CVE-2026-53875 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp