Browse / Unsafe Model Loading and Supply Chain / Code and command execution
Code and command execution
98 records in Unsafe Model Loading and Supply Chain.
- Picklescan Bypasses Unsafe Globals Check using pty.spawn A pickle payload calling pty.spawn evades the scanner because that function is missing from its unsafe globals list, enabling code execution when loaded.
- Picklescan missing detection when calling pty.spawn A pickle's __reduce__ calls pty.spawn to run shell commands, and picklescan does not flag pty.spawn, so the scan reports the file as clean.
- Picklescan is vulnerable to RCE through missing detection when calling built-in python operator.methodcaller A pickle using operator.methodcaller to call a system function evades picklescan, so loading the file runs attacker commands.
- vLLM vulnerable to remote code execution via transformers_utils/get_config Loading a model config whose auto_map points to another repository imports and runs that repository's Python even when remote code is disabled.
- Picklescan is Vulnerable to Unsafe Globals Check Bypass through Subclass Imports Pickles referencing subclasses of dangerous asyncio classes evade picklescan's exact module-name check, so their embedded payloads load and execute.
- 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 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 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 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._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.
- 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.
- LlamaIndex has Incomplete Documentation of Program Execution related to JsonPickleSerializer component Untrusted serialised data reaching the serializer's pickle fallback lets an attacker run arbitrary Python code.
- 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.
- BentoML's runner server Vulnerable to Remote Code Execution (RCE) via Insecure Deserialization Crafted POST requests make the BentoML runner server unpickle attacker-supplied data, which runs arbitrary code on the server.
- 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.
- InvokeAI Deserialization of Untrusted Data vulnerability Installing a model file through the API makes InvokeAI call torch.load on it, so a malicious checkpoint runs code when loaded.
- Kedro allows Remote Code Execution by Pulling Micro Packages Pulling a crafted micro package makes Kedro run the setup.py inside its archive during metadata extraction, executing attacker commands on the host.
- 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.
- 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.
- vllm: Malicious model to RCE by torch.load in hf_model_weights_iterator Loading a malicious checkpoint through torch.load with default settings runs attacker pickle code during model load.
- Gradio lacks integrity checking on the downloaded FRP client The FRP client binary downloaded for sharing is used without verifying a checksum or signature, so a tampered download would be executed.
- Guardrails has an arbitrary code execution vulnerability Loading a crafted XML file makes the validator pass embedded Python into eval, which runs on the victim's machine.
- MLFlow improper input validation A crafted MLproject file passes unfiltered input into execution, so attacker-supplied commands run on the machine that runs the project.
- llama-cpp-python vulnerable to Remote Code Execution by Server-Side Template Injection in Model Metadata A malicious GGUF file's chat template is rendered by an unsandboxed Jinja2 environment, so template code runs on the host.
- Keras code injection vulnerability Loading a crafted Keras model file lets embedded code run with the permissions of the host application.
- LiteLLM has Server-Side Template Injection vulnerability in /completions endpoint A malicious tokenizer_config.json supplies a chat_template that LiteLLM renders with Jinja unsafely, executing code on the server when the model is used.
- Transformers Deserialization of Untrusted Data vulnerability A malicious checkpoint containing a pickle payload is loaded by the TensorFlow model repository loader, which deserialises it and runs attacker code when loaded.
- mlflow Command Injection vulnerability A crafted MLflow configuration file, once downloaded and loaded, injects shell commands that run on the victim's machine.
- langchain vulnerable to arbitrary code execution A crafted prompt JSON file passed to load_prompt can reach Python internals through template and __subclasses__ tricks, executing code when loaded.
- Langchain vulnerable to arbitrary code execution Loading a crafted prompt through LangChain's load_prompt function causes attacker-supplied code to run on the host.