Yeti-platform versions up to 2.5.0 contain a path traversal vulnerability in the ExportTask functionality. A low-privileged authenticated user can exploit this by submitting a crafted task name that includes traversal sequences, allowing unauthorized reading of files accessible to the Yeti service account and writing export output to attacker-controlled writable paths. The vulnerability is fixed in version 2.5.1.
A path traversal vulnerability (CWE-22) exists in zeroturnaround zt-zip versions prior to 1.18.0. The Zips.get(zip).unpack().destination(outputDir).process() API constructs output file paths directly from ZIP entry names without validating that files remain within the intended output directory. This allows crafted ZIP entries with parent-directory traversal sequences to write files outside the designated output directory. The issue is fixed in version 1.18.0.
Improper Limitation of a Pathname to a Restricted Directory (CWE-22) in the Kibana Fleet feature can lead to unauthorized resource deletion via Path Traversal (CAPEC-126). A low-privileged user with Fleet agent policies write access could cause a subsequent administrative action to act on unintended resources. This can result in the deletion of resources such as Kibana spaces and other organizational assets that the low-privileged user cannot delete directly. Exploitation requires an administrator to interact with the affected Fleet interface.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in the ShareActivity component of BlueLM Copilot (com.vivo.ai.copilot) allows a malicious application installed on the same device to write arbitrary files via a crafted ACTION_SEND intent with a ContentProvider-supplied file name containing '..' sequences.
CVE-2026-92610 is a path traversal vulnerability in the Eclipse Semantic Modeling Framework (ESMF) versions 2.1.2 through 2.2.1. The Aspect Model loader improperly resolves cross-file model references by extracting directory paths from specially crafted URNs in Turtle files. This allows an attacker to cause the loader to read and merge Turtle files from arbitrary directories outside the intended model root.
The FluentCart WordPress plugin up to version 1.6.2 contains a path traversal vulnerability in its deleteFile function. Authenticated users with custom-level access or higher can exploit this flaw to delete arbitrary files on the server. This can lead to severe consequences such as remote code execution if critical files like wp-config.php are deleted.
The Contact Form Extender for Divi Builder WordPress plugin (up to version 1.0.6) contains a path traversal vulnerability that allows unauthenticated attackers to delete arbitrary files on the server. This is due to insufficient validation of file paths in the cfefd_remove_uploaded_file() function. The vulnerability is exploitable because the nonce protecting the AJAX action is exposed publicly via wp_localize_script, enabling attackers to retrieve it without authentication. Deleting critical files such as wp-config.php can lead to remote code execution.
The Academy LMS – AI Course Builder, Quizzes, Certificates & eLearning plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 4.0.1 via the 'id' parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to read the contents of arbitrary .html files on the server. The plugin appends a '.html' extension to the attacker-supplied path before reading it, so files with any other extension — including wp-config.php — are out of reach. The file's contents are returned in full in the REST JSON response's content field.
The BuddyPress XProfile Image Field plugin for WordPress versions up to 3.1.0 contains a critical path traversal vulnerability allowing unauthenticated attackers to delete arbitrary files on the server. This occurs because the plugin calls unlink() on a path derived from user-supplied signup metadata without proper path resolution or containment checks. Exploitation requires open registration and an image-type profile field on the signup form. Successful exploitation can lead to remote code execution by deleting critical files such as wp-config.php.
Grafana Mimir's Alertmanager rejects tenant-supplied receiver configurations that reference local files, but the check did not cover two HTTP client settings: http_headers.<name>.files and basic_auth.username_file. A tenant permitted to upload an Alertmanager configuration could point these fields at any file readable by the Alertmanager process. When a notification was sent, Alertmanager read the file and put its contents in a header of the outgoing request. By directing the receiver at a server they control, the tenant could read files from the Alertmanager host, such as credentials and configuration.
Exploitation requires permission to write the tenant's Alertmanager configuration. Grafana Enterprise Metrics (GEM), which is built on Mimir, is also affected. The issue is fixed in Mimir 3.1.7 and 3.2.2 and in GEM 2.17.20. GEM 2.11 through 2.16 will not receive a fix; users on those versions should upgrade to 2.17.20 or later.
Dell OpenManage Enterprise, versions prior to 4.8.0, contains an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability. A high privileged attacker with adjacent network access could potentially exploit this vulnerability, leading to Filesystem access for attacker.
CVE-2026-91910 is a path traversal vulnerability in Dell OpenManage Enterprise versions prior to 4.8.0. It allows a low privileged attacker with adjacent network access to potentially expose sensitive information by improperly restricting pathname access. The vulnerability has a medium severity with a CVSS score of 5.7.
Dell OpenManage Enterprise, versions prior to 4.8.0, contains an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability. A high privileged attacker with adjacent network access could potentially exploit this vulnerability, leading to Filesystem access for attacker.
@fastify/reply-from is a Fastify plugin that forwards requests to an upstream HTTP server. In versions up to and including 12.8.0, the plugin validated proxy paths against forward-slash dot-segments only and then built the target with the WHATWG URL parser, which normalizes a backslash and its percent-encoded form to a forward slash on the http, https, ws, and wss schemes. A path that uses backslash dot-segments therefore bypasses the traversal check and resolves to a different upstream path, so an application that scopes proxying to an upstream prefix, or relies on route guards in front of the forwarding call, can have an unauthenticated request escape the intended prefix and reach other upstream endpoints. The resulting access to unintended upstream resources is primarily a confidentiality impact with limited integrity impact. The issue is fixed in @fastify/reply-from 12.8.1, where the path is normalized and any segment resolving to a single or double dot, along with control characters and ambiguous whitespace, is rejected before the URL is constructed, and users should upgrade to 12.8.1 or later. There is no workaround other than upgrading.
@fastify/http-proxy is a Fastify plugin that proxies HTTP requests to an upstream server under a configured prefix. In versions 9.0.0 through 11.6.5, when an application uses parameterized prefix and rewritePrefix options to pin clients to a fixed upstream path, the plugin substitutes URL-decoded route parameters into rewritePrefix without re-encoding them. A parameter value that encodes a path separator together with a fragment or query delimiter therefore decodes into real separators and delimiters that inject extra upstream path segments and strip the mandatory suffix the rewritePrefix was meant to enforce, without using any dot-dot traversal. An unauthenticated remote attacker can use this to reach upstream locations outside the intended prefix, leading to path-restriction bypass and, depending on the upstream, server-side request forgery or authorization bypass in the proxied service. The issue is fixed in @fastify/http-proxy 11.6.6, and users should upgrade to 11.6.6 or later. There is no workaround other than upgrading.
@fastify/http-proxy is a Fastify plugin that proxies HTTP requests to an upstream server under a configured prefix. In versions 11.6.0 through 11.6.2, the destination validation normalizes literal backslashes before it percent-decodes the request path, so a path that encodes its backslashes and dot-segments survives the dot-segment check and is only turned into backslash and double-dot sequences after that check has passed. When the upstream resolves on a platform that treats a backslash as a path separator, the forwarded request walks out of the configured proxy prefix and reaches a sibling location on the upstream. An unauthenticated remote attacker can use this to retrieve upstream resources outside the intended prefix, so the impact is confidentiality only, and exploitation depends on the upstream's path handling. The issue is fixed in @fastify/http-proxy 11.6.3, and users should upgrade to 11.6.3 or later. This is a follow-up to the earlier prefix-escape fix, which did not account for the encoded-backslash form.
A Beta9 tenant can attach a volume when deploying a function, endpoint, or task queue. The gateway builds the host path by joining the shared volumes root, the workspace name, and the volume identifier from the stub configuration. Nothing checks that the identifier names a volume that workspace owns. Parent-directory segments in the identifier collapse the joined path to the worker's filesystem root, and the worker bind-mounts that path into the sandbox read-write unless the volume was explicitly marked read-only. A tenant with a workspace token can therefore read and write the worker's files, including other tenants' volumes stored on that machine. Confirmed against gateway 0.1.769 and worker 0.1.745. Fixed in gateway 0.1.776 and worker 0.1.756: volume identifiers and mount paths are validated before a mount is built, including for stubs saved before the check existed, and the gateway rejects a volume that does not exist or is not owned by the workspace.
The Beta9 worker serves the sandbox file API from outside the container. getHostPathFromContainerPath turns the tenant's container path into a worker path. If the unresolved path starts with a mount destination, including the default upload mount at /tmp/.beta9, the remainder is joined onto that mount's source with filepath.Join, which cleans parent-directory segments after the prefix check. A long enough run of those segments names any absolute path on the worker. A path that matches no mount is joined onto the container root and opened in the worker's own filesystem, so an absolute symbolic link such as /var/run pointing at /run is followed against the worker root. Upload, download, stat, list, find-in-files, replace-in-files, and delete-file all call this helper. A tenant with a workspace token and one running sandbox can read, write, list, and delete files on the hosting worker as root, including files of other tenants on that machine. A read-only proof downloaded the worker pod's Kubernetes service account token through the file API for a path that did not exist inside the sandbox. In the shipped remote-node manifests that service account is bound to cluster-admin. Fixed in worker 0.1.756: sandbox file operations and workspace sync open paths with os.OpenRoot, so parent-directory and symlink lookups stay inside the container root or the mount source.
CVE-2026-78189 is a path traversal vulnerability in WebDyne Perl versions from 3.007 up to but not including 3.022. It allows remote attackers to execute .psp files outside the document root by exploiting the PSGI API route fallback mechanism. The vulnerability arises because the PSGI handler does not properly sanitize path segments containing '..', enabling access to files outside the intended directory.
The Acadlix LMS plugin for WordPress versions up to and including 1.1.9 contains a path traversal vulnerability in the post_delete_assessment_file_by_id function. This flaw allows authenticated users with subscriber-level access or higher to delete arbitrary files on the server due to insufficient file path validation. The vulnerability is exacerbated by weak permission checks relying on a publicly exposed nonce, effectively allowing unauthenticated exploitation. Successful exploitation can lead to remote code execution by deleting critical files such as wp-config.php.