CVSS: 7.8EPSS: 0%CPEs: 1EXPL: 0CVE-2025-1945 – picklescan - Zip Flag Bit Exploit Crashes Picklescan But Not PyTorch
https://notcve.org/view.php?id=CVE-2025-1945
10 Mar 2025 — picklescan before 0.0.23 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. • https://github.com/mmaitre314/picklescan/commit/e58e45e0d9e091159c1554f9b04828bbb40b9781 • CWE-345: Insufficient Verification of Data Authenticity •
CVSS: 9.1EPSS: 0%CPEs: 1EXPL: 0CVE-2025-1944 – picklescan ZIP archive manipulation attack leads to crash
https://notcve.org/view.php?id=CVE-2025-1944
10 Mar 2025 — picklescan before 0.0.23 is vulnerable to a ZIP archive manipulation attack that causes it to crash when attempting to extract and scan PyTorch model archives. By modifying the filename in the ZIP header while keeping the original filename in the directory listing, an attacker can make PickleScan raise a BadZipFile error. However, PyTorch's more forgiving ZIP implementation still allows the model to be loaded, enabling malicious payloads to bypass detection. • https://github.com/mmaitre314/picklescan/commit/e58e45e0d9e091159c1554f9b04828bbb40b9781 • CWE-345: Insufficient Verification of Data Authenticity •
CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0CVE-2025-1889 – picklescan - Security scanning bypass via non-standard file extensions
https://notcve.org/view.php?id=CVE-2025-1889
03 Mar 2025 — 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 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. picklescan before 0.0.22 only considers standard pickle file extensi... • https://github.com/mmaitre314/picklescan/security/advisories/GHSA-655q-fx9r-782v • CWE-646: Reliance on File Name or Extension of Externally-Supplied File CWE-807: Reliance on Untrusted Inputs in a Security Decision •
CVSS: 8.8EPSS: 0%CPEs: 1EXPL: 1CVE-2025-1716 – picklescan - Security scanning bypass via 'pip main'
https://notcve.org/view.php?id=CVE-2025-1716
26 Feb 2025 — picklescan before 0.0.21 does not treat 'pip' as an unsafe global. An attacker could craft a malicious model that uses Pickle to pull in a malicious PyPI package (hosted, for example, on pypi.org or GitHub) via `pip.main()`. Because pip is not a restricted global, the model, when scanned with picklescan, would pass security checks and appear to be safe, when it could instead prove to be problematic. • https://github.com/shybu9/poc_CVE-2025-1716 • CWE-184: Incomplete List of Disallowed Inputs •