Browse / AI Framework and Platform Flaws / Path traversal and file access
Path traversal and file access
192 records in AI Framework and Platform Flaws.
- Flowise has an Arbitrary File Read An unauthenticated request sets the chatId parameter to a traversal path, which is joined onto the storage root because only chatflowId is validated, letting the attacker read arbitrary local files.
- Flowise has arbitrary file access due to missing chat flow id validation The chatflowId from the request body is joined into a storage path without validation, so traversal sequences read or write files outside the storage directory.
- 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.
- Ollama allows deletion of arbitrary files A crafted request to the model pull endpoint makes the server delete files at attacker-chosen locations outside the intended model store.
- LlamaIndex vulnerable to Path Traversal attack through its encode_image function Traversal sequences in the image path argument let callers read arbitrary local files through the image encoding helper.
- Gradio Allows Unauthorized File Copy via Path Manipulation The flagging feature copies any server file named in an unauthenticated predict request, without validating the supplied path first.
- H2O Vulnerable to Arbitrary File Overwrite via File Export The H2O model export endpoint accepts any destination path, letting an attacker overwrite arbitrary server files with a model file.
- H2O Vulnerable to Arbitrary File Overwrite A user-controlled export directory parameter on the model details endpoint lets requests overwrite files at arbitrary paths on the host.
- H2O Vulnerable to Execution of Arbitrary Files An exposed endpoint lets a caller encrypt arbitrary server files with a chosen key and overwrite that key, making recovery nearly impossible.
- AgentScope directory traversal vulnerability in /read-examples A crafted POST to the read-examples endpoint uses directory traversal to read any local JSON file on the server.
- AgentScope path traversal vulnerability A delete-workflow endpoint uses a user-supplied path without restricting it to the intended directory, so files outside that directory can be removed.
- AgentScope Path Traversal in /api/file The file API endpoint uses an unsanitised path parameter, letting remote callers read arbitrary files on the server.
- AgentScope path traversal vulnerability in save-workflow Workflow save and load functions accept unvalidated paths, letting attackers read and write arbitrary JSON files on the host.
- Gradio Vulnerable to Arbitrary File Deletion The audio component builds file paths from user-controlled format values, letting an attacker truncate arbitrary files to empty.
- 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.
- InvokeAI Arbitrary File Deletion vulnerability An image deletion API endpoint lets unauthorized callers delete arbitrary files on the server, including sensitive system and configuration files.
- langchain-core allows unauthorized users to read arbitrary files from the host file system ImagePromptTemplate input variables can name arbitrary server file paths, which are read into prompts and can be exposed through the output.
- PyTorch Lightning path traversal vulnerability A crafted filename sent to the upload route on Windows lets a caller write files to arbitrary locations on the host.
- 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 WebUI allows Remote Code Execution via Arbitrary File Upload to /audio/api/v1/transcriptions The upload endpoint trusts the client content type and filename, letting paths escape the upload directory and overwrite system files.
- Deep Java Library path traversal issue Archive extraction in DJL does not block absolute or cross-platform path entries, so a crafted model archive can write files outside the destination 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.
- keras Path Traversal vulnerability Extracting a crafted tar archive fetched by the file download helper writes files to paths outside the intended directory.
- 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.
- Langchain Path Traversal vulnerability A path helper does not sanitise user input, letting callers write, overwrite, read and delete files outside the intended directory.
- 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.
- Lord of Large Language Models (LoLLMs) Server path traversal vulnerability in lollms_file_system.py RAG database endpoints skip path sanitisation, so a caller can vectorise SQLite files from any directory on the host.
- Gradio has a one-level read path traversal in `/custom_component` A path parameter on the custom component endpoint can climb one directory level, letting remote requests read source files of custom components.
- Gradio has several components with post-process steps allow arbitrary file leaks Gradio file components accept arbitrary file paths from requests that bypass intended input constraints, so the server returns sensitive local files.
- 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.
- open-webui allows writing and deleting arbitrary files The pipelines upload endpoint joins an unsanitised client filename onto the cache directory, allowing files outside it to be written or deleted.
- Gradio allows users to access arbitrary files Modifying requests to a Gradio app's server lets a remote user read arbitrary files from the host machine.
- Composio Path Traversal vulnerability The file parameter in Composio's API server is not restricted to an intended directory, so crafted values can read or write files outside it.
- Ollama can extract members of a ZIP archive outside of the parent directory Zip archive entries containing parent-directory path segments are written outside the intended extraction folder.
- Flowise Path Injection at /api/v1/openai-assistants-file The file endpoint uses an unsanitised fileName parameter, letting callers read arbitrary files on the server.
- 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.
- 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.
- Vanna vulnerable to SQL Injection Unauthenticated requests reach SQL built from user input in the Flask API, letting an attacker call file-reading database functions to read local files.
- pytorch-lightning vulnerable to Arbitrary File Write via /v1/runs API endpoint Plugin tar.gz archives containing ../ entries are extracted without sanitising names, so an attacker can write files anywhere the service can reach.
- 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.
- lollms path traversal vulnerability allows overriding of config.yaml file, leading to RCE A personality config endpoint accepts traversal in its file path, letting callers overwrite the server config and turn on code-related settings.
- lollms vulnerable to dot-dot-slash path traversal in XTTS server The tts_to_file endpoint accepts unvalidated user-supplied paths, so dot-dot sequences let requests write audio files to arbitrary locations.
- 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.
- Arbitrary file deletion in litellm The transcription endpoint deletes the path taken from the uploaded filename without validation, so callers can remove arbitrary files on the server.
- 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.
- Local File Inclusion in mlflow Directory traversal sequences placed in a URI fragment evade the validation added earlier for query strings, letting requests read arbitrary local files.
- qdrant input validation failure A crafted snapshot archive containing symlinks lets recovery read and write files outside the intended data directory.
- path traversal vulnerability was identified in the parisneo/lollms-webui A crafted category parameter in the personalities listing endpoint escapes the intended folder and reveals subfolder names of arbitrary directories.
- Ollama does not validate the format of the digest (sha256 with 64 hex digits) Model blob lookups accept digests without checking their format, so crafted strings containing ../ resolve to file paths outside the blob store.