Browse / AI Framework and Platform Flaws / Path traversal and file access
Path traversal and file access
192 records in AI Framework and Platform Flaws.
- Keras archive extraction utilities allow path traversal and arbitrary file writes Archive filters check member paths against the working directory rather than the extraction target, so traversal entries escape when the process runs from root.
- Docling: Potential Path Traversal via LaTeX \includegraphics and \input Commands The LaTeX converter follows include and graphics paths without checking they stay inside the document directory, so traversal reads files outside it.
- Docling: Unsafe Zip Extraction in EasyOCR Model Download Model archive extraction does not check member paths, so a crafted zip from a compromised download source can write files anywhere the process can write.
- Docling: Unsafe XML Entity Expansion in USPTO Patent Backend A crafted USPTO patent XML with external entity references lets an attacker read server files, reach internal URLs, or exhaust resources.
- Docling: Unsafe URI and Path Handling in HTML Backend Crafted HTML can reference local files through file URIs or traversal sequences, and internal network addresses, because resource paths and redirects were not validated.
- n8n: Legacy ExecuteWorkflow Node Bypassed File Path Restrictions An authenticated user submits an arbitrary file path through the REST API to a legacy node option that skips the file-access restriction, letting them probe or load server files.
- SGLang's multimodal generation runtime has an unauthenticated path traversal vulnerability Unauthenticated upload requests with dot-dot segments in the filename let callers write files to arbitrary locations the server process can reach.
- n8n Has an Arbitrary File Read via Git Node The Git node's push operation passes user-supplied values as command-line options, letting a workflow editor read arbitrary server files.
- MLflow allows an unauthenticated remote attacker to read arbitrary files from the server's filesystem Creating a model version with a prompt tag skips source path validation, so an unauthenticated caller can register a local path that is later served as a file.
- Open WebUI Arbitrary File Write, Delete via Path Traversal Uploaded filenames containing dot-segments are not sanitised, so attackers can write files to arbitrary locations and then have them deleted.
- 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.
- Open WebUI Vulnerable to Arbitrary File Upload and Path Traversal Uploaded attachment filenames with dot-segments are not sanitised, letting an uploader write files to arbitrary locations on the server.
- BentoML has Information Disclosure in `bentoml build` via symlink traversal in the build context A symlink in an untrusted build context makes bentoml build copy the linked file's contents from outside the project into the artifact.
- 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.
- Ollama is Vulnerable to Path Traversal A crafted digest value in the model transfer handler is not sanitised before path construction, letting requests reach files outside the intended directory.
- Flowise: Path Traversal in Vector Store basePath The basePath parameter for vector store saves is used directly in filesystem writes, so authenticated users can write outside the intended directory.
- PraisonAI vulnerable to arbitrary file write via path traversal in `praisonai recipe unpack` A malicious .praison archive with ../ entries is extracted with raw tar extraction, letting it write files outside the target directory.
- 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 Arbitrary File Write (Zip Slip) in Templates Extraction Template archive entries with parent-directory segments are extracted without path checks, letting a malicious template overwrite files outside its folder.
- PraisonAI recipe registry pull path traversal writes files outside the chosen output directory A recipe bundle whose tar archive contains parent-directory entries makes the client extract files outside the chosen output folder when pulled.
- 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.
- Kedro: Path Traversal in versioned dataset loading via unsanitized version string A version string containing ../ sequences is joined into the versioned dataset path without validation, letting loads read files outside the intended directory.
- 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.
- MLFlow path traversal vulnerability A tar archive whose member paths contain traversal sequences is extracted without validation, so files can be written outside the target directory.
- LangChain Core has Path Traversal vulnerabilites in legacy `load_prompt` functions Prompt config loaders read template and example files from paths in config dicts without blocking traversal or absolute paths.
- langflow: /profile_pictures/{folder_name}/{file_name} endpoint file reading The profile picture endpoint concatenates path parameters without checks, so traversal sequences let unauthenticated callers read arbitrary server files.
- 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.
- NLTK has a Downloader Path Traversal Vulnerability (AFO) - Arbitrary File Overwrite The NLTK downloader trusts subdir and id values from remote XML indexes, so ../ sequences write files and directories outside the download folder.
- 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.
- NLTK has Arbitrary File Read via Absolute Path Input in nltk.util.filestring() A utility function opens whatever path it is given, so absolute or traversal paths let callers read arbitrary local files.
- RAGAS has an Arbitrary File Read vulnerability Ragas' multimodal handling accepts URLs in retrieved context without adequate validation, so a crafted URL can make it read local files.
- NLTK has a Path Traversal issue Corpus reader classes accept unvalidated file paths, so crafted names can reach files outside the corpus directory.
- 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.
- 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.
- 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.
- n8n Merge Node has Arbitrary File Write leading to RCE The Merge node's SQL query mode lets authenticated workflow editors write arbitrary files to the server, which can lead to code execution.
- n8n Vulnerable to Arbitrary File Write on Remote Systems via SSH Node Unauthenticated file uploads routed through workflows to SSH transfers do not validate metadata, letting filenames write to unintended remote paths.
- Unstructured has Path Traversal via Malicious MSG Attachment that Allows Arbitrary File Write Traversal sequences in MSG attachment filenames make the partitioner write attachments outside the intended output directory.
- H2O has an External Control of File Name or Path vulnerability Attacker-controlled data parsed as a file header is exported through the Frames API to arbitrary server paths, letting the attacker overwrite files such as SSH keys.
- LobeHub Vulnerable to Improper Authorization in Presigned Upload Client-supplied file name and size fields in the presigned upload request are not validated server-side, allowing writes to unintended paths and misreported storage usage.
- BentoML has a Path Traversal via Bentofile Configuration A crafted bentofile can reference paths outside the build context, so building it copies arbitrary host files such as keys into the packaged bento.
- chainlit : Chainlit allows authenticated arbitrary file reads through custom element updates An authenticated user supplies an arbitrary file path in a custom element update, and the server copies that file into a session for retrieval.
- MindsDB has improper sanitation of filepath that leads to information disclosure and DOS An absolute file path in a JSON upload body escapes the temp directory, so the server reads and moves arbitrary local files.
- n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling A publicly reachable form workflow in n8n lets unauthenticated requests read files on the underlying server.
- External Control of File Name or Path in Langflow An authenticated user can set an arbitrary fs_path in a flow request, so the server writes the flow JSON to any file path.
- 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.
- Weaviate OSS has path traversal vulnerability via the Shard Movement API The fileName value in the shard transfer logic is not validated, letting a caller read arbitrary files the service process can access.
- 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.
- InvokeAI has External Control of File Name or Path The bulk download endpoint joins a user-supplied item name into a filesystem path without canonicalisation, so unauthenticated requests can read files outside the media directory.