CyberSecBulletin

Mmaitre314 vulnerabilities

We track 6 vulnerabilities in Mmaitre314 products. 6 are rated high or critical, and none are known to be exploited. The most recent was published on September 17, 2025.

6vulnerabilities
4critical
2high
0exploited
9.1average CVSS score

Latest Mmaitre314 vulnerabilities

  • 7.8 High severity

    picklescan: Protection Mechanism Failure

    CVE-2025-10157Mmaitre314

    A Protection Mechanism Failure vulnerability in mmaitre314 picklescan versions up to and including 0.0.30 allows a remote attacker to bypass the unsafe globals check. This is possible because the scanner performs an exact match for module names, allowing malic

  • 9.8 Critical severity

    picklescan: Improper Handling of Exceptional Conditions

    CVE-2025-10156Mmaitre314EPSS 1.48%

    An Improper Handling of Exceptional Conditions vulnerability in the ZIP archive scanning component of mmaitre314 picklescan allows a remote attacker to bypass security scans. This is achieved by crafting a ZIP archive containing a file with a bad Cyclic Redund

  • 7.8 High severity

    An Improper Input Validation vulnerability in the scanning logic of mmaitre314 picklescan…

    CVE-2025-10155Mmaitre314

    An Improper Input Validation vulnerability in the scanning logic of mmaitre314 picklescan versions up to and including 0.0.30 allows a remote attacker to bypass pickle files security checks by supplying a standard pickle file with a PyTorch-related file extens

  • 9.8 Critical severity

    picklescan: Insufficient Verification of Data Authenticity

    CVE-2025-1945Mmaitre314

    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 b

  • 9.8 Critical severity

    picklescan: Reliance on File Name or Extension of Externally-Supplied File

    CVE-2025-1889Mmaitre314

    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 mali

  • 9.8 Critical severity

    picklescan: Incomplete List of Disallowed Inputs

    CVE-2025-1716Mmaitre314EPSS 1.72%

    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 glo