picklescan before 0.0.22 only considers standard pickle file extensions in the scope for its vulnerability scan. An attacker could craft a malicious model that uses Pickle and include a malicious pickle file with a non-standard file extension. Because the malicious pickle file inclusion is not considered as part of the scope of picklescan, the file would pass security checks and appear to be safe, when it could instead prove to be problematic.
The product allows a file to be uploaded, but it relies on the file name or extension of the file to determine the appropriate behaviors. This could be used by attackers to cause the file to be misclassified and processed in a dangerous fashion.
| Link | Tags |
|---|---|
| https://sites.google.com/sonatype.com/vulnerabilities/cve-2025-1889 | mitigation third party advisory exploit |
| https://github.com/mmaitre314/picklescan/security/advisories/GHSA-655q-fx9r-782v | third party advisory exploit |