CVE-2025-71353: picklescan detection bypass via torch._dynamo.guards.GuardBuilder.get

CVE-2025-71353 · Severity: high · CVSS 8.1 · Published 2026-07-04

Picklescan is a security tool used to scan Python pickle files and machine learning models for malicious code. A vulnerability in versions before 0.0.28 allows specially crafted files to bypass security checks by using a specific PyTorch function. If a user trusts the scan results and opens the file, an attacker could gain full control over the system, potentially leading to data theft or a complete system compromise.

Technologies: picklescan (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-71353 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-71353 being exploited in the wild.
How severe is CVE-2025-71353?
High severity, with a CVSS score of 8.1, published 4 July 2026.
Which products and versions are affected?
picklescan (PyPI) ECOSYSTEM:introduced=0,fixed=0.0.28.
Is there a fix for CVE-2025-71353?
Yes. picklescan (PyPI): upgrade to 0.0.28 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-71353 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2025-71353?
Check whether you run picklescan (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • picklescan (PyPI): upgrade to 0.0.28 or later
    pip install "picklescan>=0.0.28"

Technical details

A deserialization vulnerability (CWE-502) exists in picklescan due to an incomplete blocklist or detection logic. Specifically, the tool fails to identify the 'torch._dynamo.guards.GuardBuilder.get' function when used within a pickle 'reduce' method. An attacker can craft a malicious pickle file that leverages this function to execute arbitrary Python code (e.g., os.system calls). Because picklescan reports the file as safe, a victim is more likely to proceed with 'pickle.load()', resulting in arbitrary command execution. The issue is resolved in version 0.0.28.

Affected products

  • picklescan picklescan < 0.0.28

Identifiers

  • CVE-2025-71353
  • GHSA-86cj-95qr-2p4f

Timeline

  • 2025-08-22: advisory: Initial GitHub Security Advisory published
  • 2026-07-04: disclosed: NVD publication and CVE assignment
  • 2025-08-22: patched: Version 0.0.28 released to address the bypass

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.