Bypasses / Sandbox or allowlist
Sandbox or allowlist
139 cases that got past this protection.
- PraisonAI: Python Sandbox Escape via str Subclass startswith() Override in execute_code A str subclass overriding startswith defeats the underscore guard, letting attacker-supplied Python reach subprocess functions and run OS commands.
- Hugging Face Smolagents has an Injection issue The local Python executor that runs agent-generated code fails to block some constructs, so crafted code escapes its restrictions and runs commands.
- n8n has Multiple Remote Code Execution Vulnerabilities in Merge Node AlaSQL SQL Mode The AlaSQL sandbox behind the Merge node's SQL mode fails to block certain statements, letting an authenticated workflow editor read host files and run code.
- n8n has Unauthenticated Expression Evaluation via Form Node Unauthenticated form submissions with a leading equals sign make n8n evaluate the field as an expression, which can be chained with a sandbox escape to run code.
- n8n has a Sandbox Escape in its JavaScript Task Runner A workflow author can break out of the JavaScript task runner sandbox and execute code on the host outside its boundary.
- n8n has Arbitrary File Read via Python Code Node Sandbox Escape The Python Code node sandbox fails to restrict certain built-in objects, letting a workflow author read host files or execute code outside the sandbox.
- n8n: Expression Sandbox Escape Leads to RCE Crafted expressions in workflow parameters escape the expression sandbox and run system commands on the host for users who can edit workflows.
- Claude Code has Sandbox Escape via Persistent Configuration Injection in settings.json Sandboxed code could create a missing settings.json and add startup hooks that run on the host after restart.
- n8n's domain allowlist bypass enables credential exfiltration Wildcard domain patterns in the credential allowlist fail to restrict domains correctly, so credentials are attached to requests sent to unintended hosts.
- n8n Has Expression Escape Vulnerability Leading to RCE Crafted expressions in workflow parameters escape the expression evaluator's restrictions and run operating system commands on the host.
- n8n's Improper CSP Enforcement in Webhook Responses May Allow Stored XSS The CSP sandbox is not applied to some webhook and HTTP responses, so an author's HTML runs with the origin's privileges for other users.
- n8n has a Python sandbox escape An authenticated user can break out of the Python code node sandbox when task runners are enabled, running code outside the intended boundary.
- Claude Code has a Domain Validation Bypass which Allows Automatic Requests to Attacker-Controlled Domains The WebFetch trusted-domain check used prefix matching, so attacker domains that begin with a trusted name were fetched automatically, enabling data leakage.
- vm2 has a Sandbox Escape A promise callback in the sandbox is sanitised for one Promise realm but not the host-global one, letting sandboxed code reach host process objects.
- n8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox HTML returned by the Respond to Webhook node escapes the iframe sandbox meant to contain it, so injected scripts run in the editor's top-level window.
- n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node An authenticated user who can edit workflows writes Python in the Pyodide-based Code node and escapes its sandbox to run commands as the n8n process.
- Self-hosted n8n has Legacy Code node that enables arbitrary file read/write In legacy Code node mode, internal helper functions remain reachable from workflow scripts, letting editors read and write host files outside the intended restrictions.
- n8n Vulnerable to Remote Code Execution via Expression Injection Workflow expressions from authenticated users are evaluated in an insufficiently isolated context, letting them run code as the n8n process.
- @anthropic-ai/claude-code has Sed Command Validation Bypass that Allows Arbitrary File Writes A parsing error in the sed command validator lets a crafted expression pass read-only checks and write to arbitrary files.
- DSPy does not properly restrict file reads The PythonInterpreter sandbox allows file reads beyond what it should, so agent code generated from user input can read sensitive host files.
- Flowise: Authenticated Command Execution and Sandbox Bypass via Puppeteer and Playwright Packages Authenticated users can set attacker-chosen browser binary paths and arguments in Puppeteer or Playwright tools, which run on the host outside the nodevm sandbox.
- smolagents has Sandbox Escape Vulnerability in the local_python_executor.py Module Code the agent executes can abuse whitelisted modules and functions to escape the local Python sandbox and run arbitrary code on the host.
- Browser Use allows bypassing `allowed_domains` by putting a decoy domain in http auth username portion of a URL A decoy domain placed in the URL userinfo part makes the browser agent's allowed-domains check pass while it navigates to a disallowed host.
- LoLLMS Code Injection vulnerability The Calculate tool's eval sandbox can be escaped by reaching the import machinery through a frozen importer, enabling arbitrary command execution.
- TorchServe vulnerable to bypass of allowed_urls configuration Dot-segment URLs slip past the allowed_urls check, letting an attacker download a model from disallowed locations into the model store.
- llama-index-core Prompt Injection vulnerability leading to Arbitrary Code Execution Crafted prompt content gets past safe_eval's method restrictions, so model-driven input runs unauthorised code that writes files on the host.
- LangChain vulnerable to arbitrary code execution The Python AST REPL tool runs supplied scripts without adequate restriction, letting a crafted script execute arbitrary code on the host.
- vm2 Sandbox Escape vulnerability A flaw in how vm2 sanitizes Promise handlers lets code running inside the sandbox reach the host and execute arbitrary code.
- vm2 Sandbox Escape vulnerability A custom inspect function lets code inside the vm2 sandbox break out and run arbitrary Node.js code on the host.
- vm2 vulnerable to Inspect Manipulation Code running inside the vm2 sandbox can obtain a writable reference to the inspect function and change console.log options, breaking isolation.
- vm2 Sandbox Escape vulnerability Unexpected creation of a host object through Proxy handling lets sandboxed code escape vm2 and run code on the host.
- vm2 Sandbox Escape vulnerability Sandboxed code triggers an unsanitised host exception inside the exception handler, gaining host-realm objects that it can use to run arbitrary code.
- vm2 Sandbox Escape vulnerability Exception sanitisation in the vm2 source transformer can be skipped, so raw host exception objects leak and let sandboxed code reach the host context.
- vm2 vulnerable to sandbox escape Host objects passed to Error.prepareStackTrace for unhandled async errors leak out of the vm2 sandbox, letting untrusted code run on the host.
- vm2 vulnerable to Arbitrary Code Execution A WeakMap prototype lookup in vm2 gives sandboxed code access to a host object, allowing it to escape the sandbox.
- vm2 vulnerable to Sandbox Escape resulting in Remote Code Execution on host Crafted JavaScript breaks out of the vm2 sandbox and runs code with the host's privileges.
- vm2 before 3.6.11 vulnerable to sandbox escape Infinite recursion triggers a host-side RangeError whose returned object exposes the host mainModule, allowing the sandboxed code to spawn child processes.
- Sandbox bypass in vm2 Host error objects leak through stack trace generation, letting sandboxed code reach host internals and run arbitrary code.
- Prototype Pollution in vm2 Prototype pollution inside vm2 lets sandboxed code escape its boundary and run arbitrary code on the host.