Bypasses / Safe model loader or scanner
Safe model loader or scanner
91 cases that got past this protection.
- Picklescan is missing detection when calling built-in python cProfile.run A pickle payload calling cProfile.run executes arbitrary code on load, and the picklescan detector does not flag it.
- Picklescan is missing detection when calling pytorch function torch.utils.bottleneck.__main__.run_autograd_prof A crafted pickle calls a torch profiling helper that runs arbitrary code, and the scanner does not flag that function, so loading the file executes it.
- Picklescan has a missing detection when calling built-in python trace.Trace.run A pickle that calls trace.Trace.run to run a shell command is not flagged by the scanner, so loading it executes the code.
- Picklescan has a missing detection when calling built-in python profile.Profile.runctx A pickle whose reduce calls profile.Profile.runctx runs arbitrary code when loaded, and the scanner does not flag that built-in function.
- Picklescan has a missing detection when calling built-in python idlelib.autocomplete.AutoComplete.get_entity A pickle that calls idlelib AutoComplete.get_entity executes attacker code on load, and the scanner misses this built-in callable.
- Picklescan has a missing detection when calling built-in python idlelib.autocomplete.AutoComplete.fetch_completions A pickle payload calling idlelib's AutoComplete.fetch_completions is not flagged by picklescan, so loading it runs attacker-chosen code.
- Picklescan has a missing detection when calling built-in python idlelib.calltip.Calltip A pickle payload calls idlelib's Calltip.fetch_tip, which evaluates arbitrary expressions, and picklescan does not flag it, so unpickling runs attacker code.
- Picklescan is missing detection when calling built-in Python cProfile.runctx Picklescan does not flag cProfile.runctx, so a pickle that calls it to run arbitrary code passes the scan and executes on load.
- Picklescan has a missing detection when calling built-in python library idlelib.calltip.get_entity A pickle payload calls a standard library helper that evaluates strings as Python, and the scanner does not flag that call, so loading the file runs code.
- Picklescan has a missing detection when calling built-in python code.InteractiveInterpreter A malicious pickle calls the interactive interpreter's runcode method, which the scanner does not flag, so loading the file still runs attacker code.
- Picklescan has a missing detection when calling built-in python lib2to3.pgen2.grammar.Grammar.loads A pickle that calls lib2to3's Grammar.loads to run embedded code is not flagged by picklescan, so loading it executes the attacker's payload.
- Picklescan is missing detection when calling built-in python doctest.debug_script A pickle payload invokes doctest's debug_script to run embedded code, and the scanner does not flag that call.
- Picklescan has a missing detection when calling built-in python trace.Trace.runctx A pickle payload calling trace.Trace.runctx during reconstruction runs commands on load, and the scanner fails to flag it as dangerous.
- Picklescan is missing detection when calling built-in python idlelib.pyshell.ModifiedInterpreter.runcommand A pickle payload calls an idlelib function the scanner does not flag, so a malicious model passes scanning and runs code when loaded.
- Picklescan is missing detection when calling built-in python idlelib.run.Executive.runcode A pickle payload that calls idlelib's runcode evades picklescan's detection, so a scanned malicious file still executes code on load.
- Picklescan is missing detection when calling built-in python lib2to3.pgen2.pgen.ParserGenerator.make_label A pickle payload calls a lib2to3 function that the scanner does not flag, so loading the file still runs attacker-chosen code.
- Picklescan is missing detection when calling built-in python library asyncio.unix_events._UnixSubprocessTransport._start A pickle payload calling an asyncio subprocess internal is absent from the scanner's denylist, so the scan passes and loading the file runs a command.
- Picklescan has a missing detection when calling built-in python profile.Profile.run A pickle payload calling profile.Profile.run with a code string evades picklescan's detection and executes on load.
- Picklescan is missing detection when calling built-in python ensurepip._run_pip A pickle payload calling the ensurepip internal run-pip helper is not on picklescan's dangerous list, so loading the model runs shell commands.
- Picklescan missing detection when calling pytorch function torch.utils.bottleneck.__main__.run_cprofile A pickle payload calls a torch profiling helper that runs arbitrary code, and the scanner fails to flag that call, so loading the file executes it.
- Picklescan missing detection when calling pytorch function torch._dynamo.guards.GuardBuilder.get A PyTorch dynamo helper is missing from the scanner's list, so a pickle that calls it to run shell commands is reported as safe.
- Picklescan missing detection when calling pytorch function torch.fx.experimental.symbolic_shapes.ShapeEnv.evaluate_guards_expression A pickle payload calling a PyTorch symbolic shapes function evades picklescan's detection yet executes arbitrary code when loaded.
- Picklescan missing detection when calling pytorch function torch.utils.collect_env.run A pickle that calls PyTorch's collect_env run helper to execute a shell command is not detected by picklescan, so loading it runs the command.
- Picklescan missing detection when calling pytorch function torch.utils.data.datapipes.utils.decoder.basichandlers A pickle payload that routes through a PyTorch datapipes helper to call os.system evades picklescan's detection and runs code when loaded.
- Picklescan missing detection when calling pytorch function torch.jit.unsupported_tensor_ops.execWrapper A pickle's __reduce__ invokes torch.jit's execWrapper with a code string, which picklescan does not flag, so loading the file runs attacker commands.
- Picklescan is missing detection when calling pytorch function torch.utils._config_module.load_config A pickle calls a torch.utils config loader with an embedded payload that picklescan does not inspect, so unpickling runs the attacker's os.system command.
- Keras vulnerable to CVE-2025-1550 bypass via reuse of internal functionality Crafted arguments to built-in Keras modules let a malicious saved model trigger file overwrites during loading even with safe mode enabled.
- Picklescan has pickle parsing logic flaw that leads to malicious pickle file bypass A malformed STACK_GLOBAL opcode sequence makes picklescan lose track of arguments, so malicious pickle files evade detection.
- SKOPS Card.get_model happily allows arbitrary code execution Card loading silently falls back from the safe skops format to joblib for non-zip files, so a crafted model file runs arbitrary code on load.
- Skops may allow MethodNode to access unexpected object fields through dot notation, leading to arbitrary code execution at load time Chained dot-notation access in the skops loader reaches unrestricted object attributes, so a crafted model file runs code during loading.
- Skops has Inconsistent Trusted Type Validation that Enables Hidden `operator` Methods Execution Inconsistent trusted-type checks let a model file hide calls to operator functions, which chain into arbitrary code execution during loading.
- CVE-2025-24357 Malicious model remote code execution fix bypass with PyTorch < 2.6.0 A malicious checkpoint still executes code when loaded with weights-only mode on PyTorch versions before 2.6, so the vLLM safeguard is ineffective.
- PyTorch: `torch.load` with `weights_only=True` leads to remote code execution A crafted checkpoint abuses a deserialisation path that the weights-only loader still allows, so loading the file runs code.
- Picklescan Vulnerable to Exfiltration via DNS via linecache and ssl.get_server_certificate A pickle payload built from modules the scanner does not block reads local files and leaks their contents through DNS lookups during loading.
- Picklescan failed to detect to some unsafe global function in Numpy library A pickle payload calls numpy testing helpers that indirectly run arbitrary code, slipping past Picklescan because numpy was not on its blocklist.
- Picklescan missing detection when calling built-in python library function timeit.timeit() A pickle payload calls timeit.timeit as a gadget to run shell commands, evading picklescan's denylist of dangerous globals.
- Arbitrary Code Execution via Crafted Keras Config for Model Loading A malicious .keras archive with an edited config.json names arbitrary modules and functions that run during load_model, even with safe mode on.
- Zip Exploit Crashes Picklescan But Not PyTorch A zip archive with mismatched filename headers makes the pickle scanner fail while PyTorch still loads it, hiding a malicious pickle payload.
- Zip Flag Bit Exploit Crashes Picklescan But Not PyTorch Modifying ZIP flag bits makes picklescan skip a malicious pickle inside a PyTorch archive, while torch.load still reads and executes it.
- Picklescan Allows Remote Code Execution via Malicious Pickle File Bypassing Static Analysis A pickle calls pip.main to install an attacker's PyPI package during loading, evading the scanner, and that package runs its setup code on the victim.
- PyTorch Model Files Can Bypass Pickle Scanners via Unexpected Pickle Extensions A secondary pickle file with a non-standard extension inside a PyTorch archive is loaded by torch.load but skipped by the scanner, so its payload runs when the model opens.