Bypasses / Path restriction
Path restriction
109 cases that got past this protection.
- PraisonAI's symlink-extraction bypass of `_safe_extractall` writes outside `dest_dir` A tar member symlink points outside the destination and later members write through it, escaping the extraction directory.
- vm2 has a NodeVM require.root bypass via symlink traversal that allows sandbox escape Path checks use path.resolve without following symlinks while require follows them, so sandboxed code can load host modules outside the allowed root.
- Langflow Knowledge Bases API is Vulnerable to Path Traversal Bulk delete builds knowledge base paths from user-supplied names without containment checks, letting traversal sequences delete directories outside the user folder.
- PraisonAIAgents: Path Traversal via Unvalidated Glob Pattern in list_files Bypasses Workspace Boundary An agent file-listing tool validates the directory but not the glob pattern, so `..` segments reveal metadata for files outside the workspace.
- PraisonAIAgents: Arbitrary File Read via read_skill_file Missing Workspace Boundary and Approval Gate An agent influenced by injected text can call read_skill_file with arbitrary paths and read files outside the workspace without any approval prompt.
- PraisonAI has Memory State Leakage and Path Traversal in MultiAgent Context Handling The monitor builds file paths from agent ids without removing traversal sequences, and agents sharing an id also share one ledger, leaking context between them.
- PraisonAI Has Path Traversal in FileTools The file tool checks for parent-directory sequences only after normalisation has removed them, so the check never fires and any file is reachable.
- PraisonAI recipe registry publish path traversal allows out-of-root file write The registry writes uploaded bundles using a manifest-supplied name and version before validating them, so traversal sequences write files outside the registry root.
- Claude SDK for Python: Memory Tool Path Validation Race Condition Allows Sandbox Escape A symlink swapped in after path validation in the SDK's memory tool lets a local attacker redirect reads and writes outside the memory directory.
- ONNX: Arbitrary File Read via ExternalData Hardlink Bypass in ONNX load A model's external data reference points to a hardlink, which passes the symlink-only check, so loading the model can read arbitrary local files.
- ONNX: External Data Symlink Traversal The external data check follows symlinks, so a model whose external data path points through a link outside its directory gets an arbitrary file read.
- ONNX: TOCTOU arbitrary file read/write in save_external_dat The external data writer checks whether a path is a file and then opens it separately, letting an attacker swap in a symlink to overwrite arbitrary files.
- Claude SDK for TypeScript: Memory Tool Path Validation Allows Sandbox Escape to Sibling Directories A prompt-injected model supplies a path that shares the memory root's name as a string prefix, so the prefix check lets reads and writes reach a sibling directory.
- onnx Vulnerable to Path Traversal via Symlink A symlink check in the ONNX checker uses a function that follows links, so external data references can point at and read arbitrary files outside the model directory.
- Langflow has an Arbitrary File Write (RCE) via v2 API The v2 upload route takes the multipart filename unchecked and writes via naive path joining, so authenticated users can write outside the upload directory.
- Ray Dashboard is vulnerable to path traversal through its static file handling mechanism Traversal sequences in static file requests escape the dashboard's static directory, exposing arbitrary local files to remote callers.
- BentoML Vulnerable to Arbitrary File Write via Symlink Path Traversal in Tar Extraction Tar extraction validates symlink paths but not their targets, so a crafted model archive can write files outside the destination through a symlink.
- Gradio is Vulnerable to Absolute Path Traversal on Windows with Python 3.13+ On Windows with Python 3.13 or later, root-relative paths pass Gradio's safe-join check, letting unauthenticated requests read arbitrary files.
- mcp-server-git : Path traversal in git_add allows staging files outside repository boundaries The git_add tool accepts relative paths with parent-directory sequences and stages files outside the repository, which can later be committed and pushed.
- MindsDB: Path Traversal in /api/files Leading to Remote Code Execution A crafted filename in the file upload endpoint escapes the intended upload directory, and the traversal can be chained to achieve command execution.
- Claude Code has Permission Deny Bypass Through Symbolic Links Deny rules check the requested path but not its symlink target, so the agent can read a file that a user explicitly blocked.
- Claude Code Vulnerable to Command Injection via Piped sed Command Bypasses File Write Restrictions A piped sed command built with echo got past Claude Code's command validation, letting an agent in accept-edits mode write to protected paths such as .claude and outside the project.
- n8n's Improper File Access Controls Allow Arbitrary File Read by Authenticated Users Workflow authors can read sensitive files on the host, such as configuration and stored credentials, through file access nodes.
- Claude Code has a Path Restriction Bypass via ZSH Clobber which Allows Arbitrary File Writes Command validation misparses zsh clobber redirection, so injected content can make the agent write files outside the working directory without a permission prompt.
- mcp-server-git has missing path validation when using --repository flag The git MCP server did not check repo path arguments in tool calls against the configured repository, so calls could operate on other repositories.
- Weaviate OSS has a Path Traversal Vulnerability via Backup ZipSlip Backup archive entries with absolute or parent-directory paths let restore write files outside the restore root.
- Keras Directory Traversal Vulnerability A crafted tar archive uses symlink path handling to evade Keras's safe-path filter, so extraction writes files outside the target directory.
- clearml is vulnerable to Path Traversal through its `safe_extract` function The safe archive extraction routine mishandles symbolic and hard links, letting archive entries write outside the target directory.
- ZenML is vulnerable to Path Traversal through its `PathMaterializer` class The archive extraction check validates path names but ignores symlinks and hardlinks, so a crafted artifact writes files outside the target directory.
- Claude Code permission deny bypass through symlink Claude Code's deny rules matched the path string rather than the symlink target, so a denied file could be read through a symlink.
- Codex has sandbox bypass due to bug in path configuration logic A model-supplied working directory was accepted as the sandbox's writable root, letting generated commands write outside the session workspace.
- n8n symlink traversal vulnerability in "Read/Write File" node allows access to restricted files A user who can create symlinks, for example through a command node, can point the file node past its directory restrictions to read or write protected paths.
- Claude Code Research Preview has a Path Restriction Bypass which could allow unauthorized file access A prefix-based directory check accepts a sibling directory named like the working directory, so untrusted context content can steer reads outside the project.
- @modelcontextprotocol/server-filesystem vulnerability allows for path validation bypass via colliding path prefix The filesystem server's allowed-directory check is a plain prefix match, so sibling directories sharing the allowed prefix pass.
- @modelcontextprotocol/server-filesystem allows for path validation bypass via prefix matching and symlink handling Allowed-directory checks in the filesystem MCP server can be defeated by prefix matching and symlinks, exposing files outside the permitted roots.
- Gradio Path Traversal vulnerability The gradio blocked-path check fails to match NTFS alternate data stream syntax on Windows, so blocked files can still be read.
- MLflow has a Local File Read/Path Traversal in dbfs The dbfs URL handling checks only the path component, so traversal sequences in query or parameter parts escape the mount and read local files.
- Open Neural Network Exchange (ONNX) Path Traversal Vulnerability Malicious tar archives with traversal entries bypass extraction checks in download_model, letting attackers overwrite files outside the target directory.
- Gradio Blocked Path ACL Bypass Vulnerability Blocked-path checks compare case-sensitively, so changing letter case gets past the access list on case-insensitive filesystems.
- Gradio vulnerable to arbitrary file read with File and UploadButton components Omitting upload metadata in a File component payload lets a caller supply a server file path and read arbitrary files.
- Lord of Large Language Models (LoLLMs) path traversal vulnerability in the api open_personality_folder endpoint The personality folder parameter bypasses sanitize_path through traversal sequences, letting callers open arbitrary host directories.
- Gradio's `is_in_or_equal` function may be bypassed Path checks that rely on parent-directory sequences fail to normalise certain inputs, letting requests reach files outside the permitted directory.
- LoLLMS vulnerable to Expected Behavior Violation The discussion database name passes through an inadequate path sanitiser, letting crafted values point writes at locations outside the intended directory.
- lollms vulnerable to path traversal due to unauthenticated root folder settings change Unauthenticated settings changes set the XTTS root folder to the filesystem root, letting the file read endpoint serve arbitrary files and redirecting audio output elsewhere.
- Remote Code Execution via path traversal bypass in lollms Empty category and folder values let the extension path resolve to the root, so a planted config.yaml causes an __init__.py to run.
- DeepJavaLibrary API absolute path traversal DJL extracts archive entries with absolute paths to their literal location, so a malicious model artifact can overwrite system files.
- parisneo/lollms Local File Inclusion (LFI) attack The path sanitiser does not treat Windows backslash separators as traversal, so crafted paths reach file reads and deletes through endpoints such as personalities and preset deletion.
- LoLLMS Path Traversal vulnerability Weak Windows path sanitisation lets crafted input escape the intended directory and read arbitrary files.
- LoLLMS Path Traversal vulnerability Backslash-separated paths sent to the user_infos endpoint escape the intended directory on Windows, letting callers read or delete arbitrary files.
- MLflow has a Local File Read/Path Traversal bypass A hash fragment in an artifact URL slips past the earlier path check, letting the server resolve and read arbitrary local files.