Security scan bypass via enforced ZIP CRC
Published Sep 17, 2025 · Updated Sep 17, 2025
Improper exception handling in picklescan 0.0.30 and earlier allows remote attackers to bypass ZIP archive security scans. RelaxedZipFile leaves Python zipfile CRC validation enabled, so a mismatched CRC raises an exception and stops scan_zip_bytes before embedded pickle files are analyzed. The bypass requires a crafted ZIP archive; code execution follows only if a downstream application loads an unscanned malicious pickle despite the CRC error.
Summary
What happened
Improper exception handling in picklescan 0.0.30 and earlier allows remote attackers to bypass ZIP archive security scans. RelaxedZipFile leaves Python zipfile CRC validation enabled, so a mismatched CRC raises an exception and stops scan_zip_bytes before embedded pickle files are analyzed. The bypass requires a crafted ZIP archive; code execution follows only if a downstream application loads an unscanned malicious pickle despite the CRC error.
The record
- CVE
- CVE-2025-10156
- Published
- Sep 17, 2025
- Updated
- Sep 17, 2025
- Vendor
- Matthieu Maitre
- Product
- picklescan
- Classifications
- CWE-693, CWE-755
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2025CVE publishedPublication date reported by the CVE source.
- Sep 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.0.30 changes=[{"at":"0.0.31","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Bad-CRC PyTorch model archiveproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo