ZeroDay Findings
Sign inSign up

Findings

CVE-2025-1889

picklescan before 0.0.22 only considers standard pickle file extensions in the scope for its vulnerability scan.

Published Mar 3, 2025 · updated Jul 9, 2027

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.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 3, 2025 · Catalog

    Detected

    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,

  2. Jul 9, 2027 · Catalog

    Fix available

    PyPI picklescan 0 → 0.0.22

  3. Jul 9, 2027 · CIRCL Vulnerability Lookup

    Fix available

    picklescan fixed in 0.0.22

  4. Jul 9, 2027 · CIRCL Vulnerability Lookup

    Fix available

    picklescan fixed in 0.0.22

  5. Jul 9, 2027 · Catalog

    Updated

    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,

Affected

  • PyPI picklescan0 → 0.0.22

Sources

References