Skip to content
OpenAdvisories

Package · PyPI

picklescan

58 known vulnerabilities.

58 results · Feed

  • High 7.1

    picklescan - Scanning Bypass via Dynamic Eval in scan_pytorch

    picklescan before 1.0.3 contains a scanning bypass vulnerability in the scan_pytorch function that allows attackers to embed malicious magic numbers via dynamic eval using the __reduce__ trick. Attackers can craft malicious PyTorch payloads that evade pickles…

  • Critical 9.8

    picklescan - Arbitrary Code Execution via Obfuscated eval Call

    picklescan before 1.0.1 contains an unsafe deserialization vulnerability allowing unauthenticated users to execute arbitrary code by hiding eval calls nested under callable objects via getattr. Attackers can embed malicious code in pickle files that evades de…

  • High 7.5

    picklescan - Arbitrary File Read via Unsafe Pickle Deserialization

    picklescan before 0.0.35 contains an unsafe pickle deserialization vulnerability allowing unauthenticated attackers to read arbitrary server files by chaining io.FileIO and urllib.request.urlopen. Attackers can bypass RCE-focused blocklists to exfiltrate sens…

  • Critical 9.8

    picklescan - Arbitrary Code Execution via profile.run() Blocklist Bypass

    picklescan before 1.0.4 contains an incomplete blocklist for the profile module that fails to block the module-level profile.run() function, allowing attackers to achieve arbitrary code execution via exec(). Attackers can craft malicious pickle files calling …

  • Critical 10.0

    picklescan - Universal Blocklist Bypass via pkgutil.resolve_name

    picklescan before 1.0.4 fails to block pkgutil.resolve_name, allowing attackers to bypass the entire blocklist by resolving any dangerous function through indirect REDUCE calls. Remote attackers can invoke any blocked function such as os.system, builtins.exec…

  • Critical 9.8

    picklescan - Detection Bypass via STACK_GLOBAL Opcode Parsing Logic Flaw

    picklescan before 0.0.27 contains a parsing logic error in the _list_globals function when handling STACK_GLOBAL opcodes, failing to track arguments in the correct range and allowing malicious pickle files to bypass detection. Attackers can craft pickle files…

  • Critical 9.8

    picklescan - Remote Code Execution via Unblocked ctypes Module

    picklescan before 0.0.33 fails to block the ctypes module, allowing attackers to achieve remote code execution by invoking direct syscalls and accessing raw memory. Attackers can craft malicious pickle files using ctypes.WinDLL to load kernel32.dll and execut…

  • High 8.8

    PickleScan - Unsafe Globals Check Bypass via pty.spawn Function

    PickleScan before 0.0.33 fails to include the pty.spawn function in its unsafe globals list, allowing attackers to bypass security checks. Malicious actors can craft pickle payloads using pty.spawn to achieve arbitrary code execution when files are processed …

  • Critical 9.8

    picklescan - Remote Code Execution via Incomplete Disallowed Inputs

    picklescan before 0.0.33 contains an incomplete deny-list that fails to block pydoc.locate and operator.methodcaller functions, allowing attackers to bypass security checks. Remote attackers can craft malicious pickle files using these unblocked functions to …

  • Critical 9.8

    picklescan - Arbitrary File Writing via distutils Module Bypass

    picklescan before 0.0.33 contains an arbitrary file writing vulnerability that allows attackers to bypass the dangerous blocklist by using distutils.file_util.write_file. Attackers can construct malicious pickle objects to overwrite critical system files and …

  • High —

    Picklescan missing detection when calling pty.spawn

    ### Summary Using pty.spawn, which is a built-in python library function to execute arbitrary commands on the host system. ### Details The attack payload executes in the following steps: First, the attacker craft the payload by calling to `pty.spawn` function…

  • Critical 9.3

    PickleScan Bypasses Unsafe Globals Check Using Submodule Imports

    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 mali…

  • Critical 9.3

    PickleScan Security Bypass via Bad CRC in ZIP Archive

    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 Redun…

  • Critical 9.3

    PickleScan Security Bypass Using Misleading File Extension

    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 exten…

  • Medium 6.8

    Picklescan Vulnerable to Exfiltration via DNS via linecache and ssl.get_server_certificate

    The unsafe globals in Picklescan before 0.0.25 do not include ssl. Consequently, ssl.get_server_certificate can exfiltrate data via DNS after deserialization.

  • Medium 5.3

    picklescan - Zip Flag Bit Exploit Crashes Picklescan But Not PyTorch

    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 …

  • Medium 5.3

    picklescan ZIP archive manipulation attack leads to crash

    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 li…

  • Medium 5.3
    CVE-2025-1716 Public exploit

    picklescan - Security scanning bypass via 'pip main'

    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 gl…