IBM Langflow OSS 1.0.0 through 1.10.3 does not properly validate the username field, allowing attackers to inject path traversal sequences and bypass containment checks. This enables multiple severe impacts, including arbitrary directory deletion, cross-tenant data destruction, and JWT signing key deletion leading to session invalidation.
IBM Langflow OSS versions 1.0.0 through 1.10.3 contain a path traversal vulnerability in the Knowledge Bases API endpoint. This flaw allows an authenticated attacker to create directories and write files anywhere on the server filesystem by supplying crafted knowledge base names without proper sanitization. The vulnerability has a medium severity rating with a CVSS score of 5.4. No official patch or remediation guidance is currently available.
IBM Langflow OSS 1.0.0 through 1.10.3 allows users to read arbitrary files from the server filesystem, including other users' uploaded documents, the JWT signing secret, the SQLite database, and process environment variables, by sending a crafted MCP `resources/read` request with a URL-encoded path traversal sequence in the filename.
A cross-site scripting vulnerability in the Query Console of Progress MarkLogic Server before 11.3.6 and 12.0.3 allows a remote attacker who lures an authenticated administrator to a crafted URL to execute arbitrary JavaScript in the administrator's browser session, capture credentials, and perform privileged actions on the administrator's behalf.
The Content Egg – Affiliate Product Importer & Price Comparison WordPress plugin up to version 11.3.0 contains a path traversal vulnerability that allows authenticated users with author-level access or higher to delete arbitrary files on the server. This occurs because the plugin insufficiently validates the 'img_file' field, enabling crafted input to bypass filtering and cause deletion via PHP's unlink() function. This vulnerability can lead to denial of service or potentially remote code execution if critical files are deleted.
Fledge's backup-restore upload handler, upload_backup (python/fledge/services/core/api/backup_restore.py), calls tarfile.extractall(temp_path) on an admin-uploaded tar archive with no filter argument and no per-member path validation. Requires the admin role (@has_permission("admin")).
Zigbee2MQTT's ExternalJSExtension.getFilePath (lib/extension/externalJS.ts) joins a parameter received via an MQTT message (topic zigbee2mqtt/bridge/request/extension/save) into the extensions base path using path.join(basePath, name) with no sanitization. The extension handler only validates that the name ends in .js/.mjs/.cjs, writes the file, and then dynamically imports it via Node.js import, achieving remote code execution.
OpenPLC Runtime v3's compile_program function (webserver/openplc.py) parses directives from uploaded Structured Text (.st) program files and writes the referenced content to with no validation that file_path stays within the ./core directory. A path-validation function, validate_file_path, exists elsewhere in the codebase (webserver/credentials.py) but is never invoked from compile_program, leaving the sink unprotected.
CVE-2026-46581 is a high severity path traversal vulnerability in Eclipse Mojarra version 2.3. The issue arises from improper URL handling in the DefaultFaceletFactory component, which fails to sanitize or block remote URLs. This flaw allows an attacker to specify a remote Facelet URL that the server includes and processes with its privileges, potentially exposing restricted files such as WEB-INF/web.xml or /etc/passwd.
Eclipse Theia versions up to and including 1.73.1 contain a directory traversal vulnerability in the @theia/filesystem backend HTTP file-download endpoints. These endpoints convert client-supplied URIs directly to filesystem paths without restricting access to the workspace or allowed roots. In browser deployments, token enforcement is ineffective on HTTP requests, allowing unauthenticated clients to read any file accessible by the backend process, including sensitive files outside the workspace. Electron mode is not affected by this vulnerability via this path.
Eclipse Theia versions up to and including 1.73.1 have a vulnerability in the @theia/filesystem backend where an unauthenticated attacker can perform arbitrary file writes outside the workspace via a specially crafted POST /file-upload request. This occurs because the handler accepts an absolute path from user input without workspace confinement or authentication. Browser deployments are affected due to insufficient token enforcement on HTTP requests, enabling cross-origin web pages to exploit this without credentials. Electron mode is not affected by this issue. The vulnerability has a high severity CVSS score of 8.8 and can lead to remote code execution by overwriting critical files such as ~/.bashrc.
Eclipse Theia versions 1.66.0 through 1.73.1 contain a directory traversal vulnerability in the @theia/plugin-ext backend. The HTTP endpoint /hostedPlugin/:pluginId/:path(*) improperly resolves file paths without verifying that the resolved path remains within the plugin directory. This allows unauthenticated network attackers to retrieve arbitrary files readable by the Theia backend process by sending encoded traversal sequences. Plugin IDs are deterministic, enabling attackers to target built-in plugins without prior system knowledge. The vulnerability has a high severity with a CVSS score of 7.5.
audiobookshelf's authentication-exemption check (server/routers/Auth.js) matches unauthenticated-allowed GET routes against req.path via a regex requiring a literal /items/:id/cover or /authors/:id/image shape, where req.path retains %2F sequences URL-encoded. CacheManager.handleCoverCache then joins this decoded value into a cache file path and streams the result before any database-backed ownership check.
The pocketflow-coding-agent cookbook example in The-Pocket/PocketFlow implements a helper as a thin os.path.join(workdir, p) wrapper with no canonicalization or containment check, used unguarded by the ReadFile, ListFiles, PatchRead, and PatchApply file-access tools. Severity reflects that this affects an illustrative cookbook example rather than a core library API; applications that copy this pattern into production are affected.
The Custom Fields WordPress plugin before 1.5.1 does not validate a user-supplied file path before deletion, allowing unauthenticated users to delete arbitrary files on the server (such as wp-config.php), which can lead to a full site takeover.
A path traversal vulnerability exists in TryGhost Ghost CMS versions from 0.10.0 up to but not including 6.54.1. This flaw allows a staff user to write files outside the intended uploads directory via custom theme uploads, potentially altering the installation's behavior. The issue is fixed in version 6.54.1.
Ghost, a Node.js content management system, contains a path traversal vulnerability in versions from 1.20.1 up to but not including 6.54.1. An administrator-level user could exploit this flaw by supplying a crafted database backup filename containing path separators, allowing remote overwriting of certain filesystem files. This vulnerability affects the integrity and availability of the system. The issue is fixed in version 6.54.1.
CVE-2026-47682 is a path traversal vulnerability in the CVAT open source annotation tool. Versions from 1.6.0 up to but not including 2.65.0 allow an attacker with write access to a configured cloud storage, or the ability to add new cloud storages, to overwrite arbitrary files on the server filesystem. This vulnerability has been fixed in version 2.65.0.
pdm is a Python package and dependency manager supporting the latest PEP standards. Versions prior to 2.27.0 are vulnerable to path traversal through write_to_fs. InstallDestination.write_to_fs() in src/pdm/installers/installers.py overrides the base class to add symlink/hardlink support but replaces the safe _path_with_destdir() (which validates via Path.resolve() + is_relative_to()) with a bare os.path.join() that performs no path validation. A malicious wheel with traversal entries can write arbitrary files. This issue has been fixed in version 2.27.0.
NVIDIA Dynamo for Linux contains a vulnerability in the image loading component where an attacker may cause improper limitation of a pathname to a restricted directory. A successful exploit of this vulnerability might lead to information disclosure.