Path Traversal

Path traversal in AWX's project_archive action plugin allows arbitrary file writes to execution node filesystems outside the intended project directory. Red Hat Ansible Automation Platform 2 is affected when processing zip or tar archives whose member filenames contain directory traversal sequences. An attacker who controls archive content - via admin-level project configuration, a compromised upstream archive source, or a man-in-the-middle attack on an unencrypted HTTP fetch - can write files as the extraction user and escalate to remote code execution through cron entries, SSH authorized_keys injection, or playbook content poisoning. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV.

Path traversal in RansomLook's GroupPost.get API handler allows an attacker controlling a malicious upstream instance to exfiltrate arbitrary files readable by the RansomLook process, including configuration secrets and API credentials. The screen field stored in the database is concatenated directly with the application's source/ directory path without boundary validation, enabling traversal sequences such as ../config/generic.json to escape the intended directory. No public exploit code has been identified at time of analysis and the vulnerability is not listed in CISA KEV, but the federation import mechanism means a compromised upstream instance can poison a victim's database without holding any account on the victim system.

Path traversal in webpack-dev-middleware bypasses the incomplete CVE-2024-29180 fix by embedding dot-dot sequences within path segments (e.g., 'assets..') rather than as standalone segments, causing the UP_PATH_REGEXP guard to pass while the subsequent fixed-offset slice produces a parent-directory component that resolves above outputPath on the physical filesystem. Affected versions are precisely 5.3.4+, 6.1.2+, and 7.1.0+ - the releases that introduced the original guard-and-slice logic intended to fix path traversal. Exploitation is constrained to non-default configurations where publicPath lacks a trailing slash and the physical filesystem is in use via writeToDisk: true or a custom outputFileSystem; no public exploit identified at time of analysis, though a functional PoC for the predecessor attack class exists in GHSA-wr3j-pwj9-hqq6.

Path traversal in the Mercado Pago Node.js SDK allows attackers who can influence payment, refund, or disbursement identifiers handled by merchant applications to redirect outbound API calls to unintended Mercado Pago endpoints, carrying the merchant's own access token. The affected clients - payment (get, capture, cancel), paymentRefund (create, total, list, get), advancedPayment (get, capture, cancel, update, updateReleaseDate), and disbursementRefund (create, createAll, listAll) - construct API paths via unencoded template literals, allowing dot-dot sequences and question marks to traverse to alternate endpoints or append attacker-chosen query parameters. No public exploit has been identified at time of analysis, and exploitation is conditional on merchant applications forwarding unvalidated, user-supplied identifiers directly to the SDK.

Unauthenticated arbitrary file deletion in ShopBuilder Pro - Elementor WooCommerce Builder Addons plugin versions 2.2.0 and earlier allows any remote attacker to delete arbitrary files on the underlying WordPress server without credentials. The root cause is a path traversal weakness (CWE-22) in a network-exposed endpoint that fails to sanitize user-supplied file paths, enabling traversal outside the plugin's intended file scope. No active exploitation has been confirmed in CISA KEV, and no public exploit code has been identified at time of analysis; however, the trivial exploitation conditions (no authentication, no user interaction) make this a high-priority patching target for any site running the affected plugin.

Unauthenticated arbitrary file deletion in WooCommerce File Approval plugin (versions through 10.7) allows any remote attacker to delete arbitrary files on the underlying server without credentials or user interaction. The path traversal root cause (CWE-22) enables attackers to escape the plugin's intended file handling scope, with the CVSS S:C scope-change indicator confirming that files outside the plugin's own directory — including WordPress core files, configuration files, or OS-level files accessible to the web server process — can be targeted. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the zero-complexity, unauthenticated attack surface makes this a high-priority remediation target for any site running the affected plugin.

Unauthenticated arbitrary file download in the Super Forms WordPress plugin (versions up to and including 6.3.315) exposes any file readable by the web server process to remote attackers without any credentials. The root cause is a path traversal flaw (CWE-22) in a file download endpoint that fails to sanitize user-supplied path parameters, enabling directory traversal sequences to escape the intended file root. No public exploit or CISA KEV listing is confirmed at time of analysis, but the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates trivial, unauthenticated remote exploitation with no special conditions required on default plugin installations.

Host root code execution in Canonical LXD arises from a path-traversal flaw in instance template processing, letting an attacker with container edit permissions - or any user who launches a maliciously crafted image - overwrite arbitrary root-owned files on the host. The root cause is a validate-then-open mismatch: LXD checks template target paths against a confined os.Root handle but then creates the file via os.Create using the raw, unconfined string path. No public exploit has been identified at time of analysis, but the CVSS 9.9 rating and container-to-host scope change make this a critical container-escape.

Path traversal in achorein expo-share-intent up to version 8.0.0 allows a local attacker to write files outside the intended cache directory by supplying a crafted `_display_name` value during Android file sharing operations. The `getDataColumn` function in `ExpoShareIntentModule.kt` constructed file paths directly from the unvalidated content-provider display name, enabling directory escape via sequences such as `../../`. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; a vendor-released patch (v8.0.1) resolves the issue.

Unauthenticated remote file read in 4MOSAn Management Center (all versions prior to build 20260621) allows any network-reachable attacker to download arbitrary system files via a Relative Path Traversal flaw (CWE-23). The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H) confirms no authentication, no user interaction, and no special configuration is required to trigger the vulnerability. A vendor-issued patch was released as of build 20260621 per TWCERT advisory; no public exploit code or CISA KEV listing has been identified at time of analysis.

Path traversal in exceljs-hardened before 5.0.0 allows unauthenticated attackers to read arbitrary files from the server filesystem by supplying crafted paths to the Workbook.addImage() function, which performs no input validation before passing the value to Node.js file system APIs. Any Node.js application that exposes this function to user-controlled input is at risk of exposing secrets, credentials, configuration files, and any other content readable by the process. No public exploit has been identified at time of analysis; vendor-released patch is available as version 5.0.0.

OneNav 1.2.4's import_link() function allows any authenticated user to delete arbitrary files on the host system via path traversal, scoring CVSS 8.1 with High integrity and availability impact. Publicly available exploit code exists per SSVC assessment (exploitation: poc), though EPSS probability remains very low at 0.14% (4th percentile), indicating limited widespread exploitation activity. The attack requires only low-privilege authentication over the network with no user interaction, making it accessible to any registered user of an exposed OneNav instance.

Remote code execution in GitLab CE/EE package registry exposes instances across three active version branches to full host compromise by an authenticated low-privilege user. Path traversal (CWE-22) in the package registry component allows directory escape and arbitrary file write under certain server-side conditions, with CVSS scope change (S:C) confirming that impact extends beyond the GitLab application to the underlying host. A publicly available exploit exists via HackerOne report 3754194, though this vulnerability is not listed in the CISA KEV catalog at time of analysis.

Directory traversal in WebToffee WooCommerce PDF Invoices, Packing Slips, Delivery Notes & Shipping Labels plugin (all versions ≤ 4.9.8) allows subscriber-level authenticated attackers to read arbitrary server files via the get_image_src_in_base64 function. The exfiltration channel is particularly stealthy: base64-encoded file contents are embedded into cached invoice HTML and retrieved through the plugin's own legitimate Print/Download endpoints using only a valid nonce and access key, potentially bypassing WAF rules that inspect request paths. No public exploit or CISA KEV listing is identified at time of analysis; however, the trivially low privilege bar - any registered WooCommerce customer qualifies - combined with high-value targets like wp-config.php credentials makes this an operational priority for any public-facing WooCommerce store.

Path traversal in the Fabrik application-builder extension for Joomla (all versions from 1.0.0 through 4.7.2, fixed in 4.7.3) lets remote attackers manipulate file paths through the image element to reach files outside the intended directory. The vendor's CVSS 4.0 score of 10.0 with PR:N indicates unauthenticated network exploitation, though there is no public exploit identified at time of analysis. The affected component is a form/data-application builder, so exploitation could expose or tamper with files on the Joomla host.

StreamBackedCorpusView in NLTK before 3.10.0 allows arbitrary local file reads by calling Python's builtins.open() directly, fully bypassing the pathsec.ENFORCE security boundary regardless of how that control is configured. Web applications and services built on NLTK that pass externally controlled values to the fileid argument are at risk of having sensitive system files, credentials, and configuration data read by remote attackers. A vendor-released patch is available in NLTK 3.10.0; no public exploit has been identified at time of analysis.

Path traversal and pickle deserialization protections in NLTK before 3.10.0 are effectively disabled by default - pathsec.py sets ENFORCE=False, causing all security validation to emit warnings rather than raise blocking exceptions. Any application using NLTK to process untrusted file paths or serialized data is exposed unless operators have explicitly overridden this default. No public exploit has been identified at time of analysis, but the attack surface is significant wherever NLTK handles attacker-controlled inputs, particularly given that Python pickle deserialization can enable arbitrary code execution.

Path traversal in NLTK's FramenetCorpusReader and NKJPCorpusReader (all versions before 3.10.0) enables unauthenticated network-reachable attackers to read arbitrary XML files accessible to the application process by supplying crafted selectors or poisoned index state to methods including frame_by_name, doc, lu, and header. The CVSS 4.0 score of 8.2 reflects high confidentiality impact (VC:H) tempered by high attack complexity (AC:H) and a required attack target condition (AT:P), meaning exploitation depends on application code that exposes these specific corpus reader methods to external input. No public exploit code and no CISA KEV listing have been identified at time of analysis.

Symlink-based path traversal in NLTK's FramenetCorpusReader before version 3.10.2 permits attackers with write access to a corpus subdirectory to read arbitrary XML files outside the intended corpus root. The flaw exists because path validation in frame_by_name(), _lu_file(), and doc() checks only for path separator characters in filenames but does not resolve symbolic links before access, allowing a separator-free symlink name to bypass the guard and dereference an out-of-root target. No public exploit code or CISA KEV listing has been identified; the provided CVSS 4.0 vector of PR:N/AV:N is inconsistent with the filesystem write prerequisite described and warrants verification with the vendor.

Symlink-based arbitrary file read in NLTK's IPIPANCorpusReader exposes files accessible to the running process on systems where untrusted local users can write to corpus root directories. Affected NLTK versions before 3.10.2 fail to follow symlinks through the nltk.pathsec validation layer when IPIPANCorpusReader methods - channels(), domains(), categories(), or fileids() - resolve filenames, allowing the symlink target to be read instead of the intended corpus file. No public exploit or CISA KEV listing has been identified at time of analysis; real-world risk is bounded by the local attack vector and the requirement for write access to the corpus directory.

Path traversal in NLTK's CrubadanCorpusReader (versions 3.9.4 through 3.10.2) allows an attacker who controls a malicious corpus package to read arbitrary file contents outside the corpus root directory via the lang_freq interface. The vulnerability arises because _load_lang_ngrams bypasses NLTK's pathsec containment by calling the builtin open() instead of the pathsec-validated opener, enabling os.path.join to silently discard the corpus root prefix when an absolute path is supplied as the crubadan_code value. No public exploit exists and no KEV listing is present; a vendor patch is available in 3.10.3.

Arbitrary file deletion in SiYuan before v3.7.4 allows authenticated administrators to recursively destroy any file or directory accessible to the SiYuan kernel process by supplying an unsanitized absolute path to the /api/search/removeTemplate endpoint, which passes the value directly to Go's os.RemoveAll. All SiYuan releases prior to v3.7.4 are confirmed affected per vendor advisory GHSA-w938-w7m4-qrj8. No public exploit or CISA KEV listing exists at time of analysis, but the high integrity and availability impact - including potential downstream filesystem destruction beyond the application - makes admin credential hygiene the critical control.

Server-Side Request Forgery in the Mailgun for WordPress plugin (versions up to and including 2.2.0) lets unauthenticated attackers coerce the WordPress server into making authenticated requests to arbitrary Mailgun API endpoints using the site's own stored API key. Because the add_list() function trusts user-controlled array keys from $_POST['addresses'] and only runs them through sanitize_text_field(), an attacker can path-traverse to any Mailgun endpoint - notably creating inbound email-forwarding routes to intercept password-reset messages and take over the administrator account. Reported by Wordfence with a CVSS of 9.8; no public exploit identified at time of analysis and no CISA KEV listing.

Arbitrary file read in the Tutor LMS WordPress plugin (all versions before 4.0.6) allows authenticated instructors to retrieve any file on the server — including files outside the web root — by exploiting a missing path validation check in the plugin's media streaming functionality. Critically, readable targets include wp-config.php, which exposes database credentials and WordPress authentication keys and salts; possession of these constants enables an attacker to forge valid session cookies for any account, including site administrators. No public exploit has been identified at time of analysis, and the EPSS score of 0.18% (8th percentile) reflects low observed exploitation activity, but the cascading impact path from instructor account to full site compromise makes patching urgent for any site with open instructor registration.

Path traversal in Arc Enterprise's Raft finite state machine allows low-privileged cluster peers to register arbitrary file paths via manifest-registration proposals, bypassing all path validation in the applyRegisterFile handler (internal/cluster/raft/fsm.go). All Arc Enterprise deployments running in cluster mode prior to version 2026.06.1 are affected. No public exploit code has been identified at time of analysis, but successful exploitation enables data writes outside the configured storage backend root, directly undermining storage isolation guarantees.

Path traversal in LeafWiki's asset rename endpoint allows authenticated editors to relocate any file readable by the server process into a page's public asset directory, making it downloadable over HTTP. All releases from 0.3.0 through 0.10.0 (CPE: cpe:2.3:a:perber:leafwiki:*:*:*:*:*:*:*:*) are affected; version 0.10.1 contains the fix. No CISA KEV listing or public exploit code has been identified at time of analysis, but the low exploitation complexity and high-impact outcome - including potential exposure of the application database - make prompt patching urgent for any multi-user deployment.

Path traversal in Atlantis workspace handling (versions 0.19.8 through 0.44.x) allows authenticated users to escape the intended workspace directory boundary, triggering os.RemoveAll and os.MkdirAll operations on arbitrary filesystem paths with Atlantis process privileges. A crafted workspace value such as '../../../../../../../../tmp/f1-canary' - supplied via repository atlantis.yaml or authenticated /api/plan API input - causes Atlantis to operate on out-of-bounds directories before Terraform rejects the invalid workspace name. A working proof-of-concept is documented in GHSA-26w5-6g95-gj28; the vulnerability is not in CISA KEV and no public exploit kit has been identified at time of analysis.

Infracost's template engine prior to v0.10.45 allows repository-controlled symlinks to escape the checkout directory, enabling any contributor with repository write access to read files accessible to the CI/CD runner. The vulnerable template functions - readFile, pathExists, isDir, and matchPaths in internal/config/template/parser.go - relied on lexical filepath.Abs normalization and leaf-only os.Lstat checks that failed to resolve intermediate directory symlinks, so a path like evil/secret passes validation while physically exiting the repository root. Captured file contents are rendered into Infracost configuration output and surfaced via the Infracost dashboard or pull request comments; no public exploit identified at time of analysis, and vendor-released patch is confirmed in v0.10.45.

Path traversal in Omnigent AI agent framework (versions prior to 0.3.0) allows authenticated users to escape the session workspace by uploading a crafted agent bundle with an absolute or traversal-containing os_env.cwd value, exposing host filesystem contents and runner environment secrets. The vulnerability chain spans four source files - parser.py, validator.py, resource_registry.py, and os_env.py - and the security boundary collapses specifically when OMNIGENT_RUNNER_WORKSPACE is unset on the runner. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis; a vendor-confirmed fix was released in v0.3.0.

Symlink-following arbitrary file write in ONNX's save_external_data function (onnx/external_data_helper.py) allows a local attacker with write access to a shared directory to redirect a victim's model serialization writes to any file the victim can modify — including ~/.ssh/authorized_keys, cron entries, and application configuration files. All ONNX releases up to and including 1.20.1 (pip/onnx) are affected; the vendor-released patch is 1.21.0. Publicly available exploit code is confirmed via the GHSA advisory, and CISA has published a CSAF advisory (va-26-233-01) covering this issue, indicating heightened government-sector awareness.

Path traversal in Infinite Image Browsing (zanllp/infinite-image-browsing), a Stable Diffusion WebUI extension, exposes arbitrary files outside configured allowed directories to unauthenticated remote attackers by exploiting a missing trailing path separator in the is_path_trusted prefix comparison. The bypass is only exploitable in network-exposed deployments - those started with --share, --ngrok, --listen, or --server_name flags, or with IIB_ACCESS_CONTROL=enable - which are precisely the configurations relying on this confinement for protection. No public exploit has been identified at time of analysis, but the bypass is trivially replicable from the public patch diff; an upstream fix is confirmed at commit 4057a624.

Unauthenticated arbitrary directory listing in the Gallery element of the YOOtheme Zoo extension for Joomla exposes server-side directory structures to any remote, unauthenticated attacker on sites running Zoo versions prior to 4.1.66. The path traversal vulnerability (CWE-22) allows crafted requests to enumerate directories outside the intended scope of the Gallery element, potentially revealing sensitive filesystem layout including configuration paths, user data directories, or other installed components. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.

Arbitrary file read in YOOtheme Pro (Joomla extension) versions 2.3.0 through 5.0.40 allows privileged authenticated users to access files outside the intended directory by exploiting glob-based pattern injection in the Filesystem source's path filter. The vulnerability requires high-privilege credentials on the Joomla backend, limiting the attack surface to trusted but potentially malicious insiders or compromised administrator accounts. No public exploit code or CISA KEV listing has been identified at time of analysis, though the CVSS 4.0 score of 7.0 reflects the high confidentiality impact from unrestricted file reads.

Path traversal in JuiceFS filestore backend (pkg/object/file.go) enables arbitrary file writes outside the configured storage root during sync operations. The path() helper joined incoming object keys onto the storage root via filepath.Join or filepath.Clean without verifying the resolved result remained within that root, affecting Put, Get, Head, Delete, Chmod, Chown, Symlink, and Readlink. An attacker who can plant object keys containing traversal sequences such as ../../etc/cron.d/backdoor into a source bucket - a shared, public, or compromised bucket - causes a juicefs sync to write attacker-supplied content to arbitrary filesystem paths on the operator's host. No public exploit identified at time of analysis; an upstream fix is available via commit 0bcd70b3d and pull request #7425.

Arbitrary file write and recursive directory deletion in SiYuan note-taking application before v3.7.4 stems from missing validation of the packageName parameter in the Bazaar marketplace install and uninstall endpoints. An authenticated administrator can supply directory-traversal sequences to write files to any filesystem location (install) or recursively delete arbitrary directories (uninstall), enabling remote code execution and destructive impact. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.

Path traversal in the misp-stix Python library allows an attacker who can supply crafted STIX 2 content to escape the configured object-template directory during PyMISP template resolution, reading arbitrary files accessible to the conversion process and copying their contents into converted MISP objects. All MISP deployments performing STIX 2 import or MISP-to-STIX 2 export via misp-stix are affected, with the flaw carrying a CVSS 4.0 score of 8.8. No public exploit or CISA KEV listing exists at time of analysis, but the vulnerability's persistent re-triggering pathway - where a poisoned MISP event is later re-exported by a higher-privilege process - represents a privilege-escalation risk beyond what the base score alone reflects.

Path traversal in the `apport-unpack` utility of Canonical Apport enables arbitrary file creation and overwrite by exploiting attacker-controlled key names embedded in crafted crash report files. Affected versions span all Apport releases before 2.28.4, 2.34.2, and 2.36.0 - software that ships by default with Ubuntu desktop and server editions. An attacker who delivers a malicious `.crash` file and induces a user or automated pipeline to unpack it can write files to any location accessible by the executing user, creating a realistic privilege-escalation primitive on multi-user or developer Ubuntu systems. No public exploit is identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.

Path traversal in IBM AIX 7.2/7.3 and PowerVM VIOS 4.1 enables remote, unauthenticated attackers to bypass directory-based access controls by supplying manipulated pathname inputs that escape restricted filesystem boundaries. The vulnerability carries a CVSS 3.1 score of 4.8 (Medium) with high attack complexity (AC:H), which constrains opportunistic exploitation while still leaving targeted attacks viable without requiring credentials. No public exploit code or active exploitation has been identified at time of analysis; IBM has published an advisory at their support portal (https://www.ibm.com/support/pages/node/7283858).

Privilege elevation in Microsoft Azure Logic Apps allows an unauthenticated, remote attacker to escalate privileges by abusing a path-traversal flaw (CWE-22) that fails to restrict a supplied pathname to its intended directory, provided a victim is lured into interacting (UI:R). Rated CVSS 9.6 with a changed scope, indicating impact beyond the initially vulnerable component. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.

Privilege elevation in Microsoft Fabric lets an authenticated, low-privileged user abuse a relative path traversal weakness (CWE-23) over the network to reach resources outside their intended scope and gain higher privileges. Microsoft rates this CVSS 9.9 with a scope change, reflecting that a compromised tenant identity can cross authorization boundaries in the multi-tenant analytics platform. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the near-maximum score and low attack complexity make it a high-priority fix.

Path traversal in Dockge's stack name handling allows authenticated users to exfiltrate secrets from .env and Compose files belonging to any directory the server process can reach, and to recursively delete those directories. The flaw exists because validate() - which enforces a strict name allowlist - is only called from the save() code path; the socket handlers that service read and delete operations pass the raw user-supplied name directly to Stack.getStack without sanitization. Because Dockge routinely runs as root with access to the Docker socket, the reachable set encompasses the full host filesystem, not just managed stacks. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the bypass is mechanically trivial for any authenticated user.

Path traversal in Apple's open-source container runtime (versions before 1.2.0) enables a malicious builder peer to request host files by crafted names that resolve outside the build context, leaking arbitrary host filesystem contents. The CVSS vector (AV:N/AC:L/PR:L) indicates network-accessible exploitation by a low-privileged builder peer with no user interaction required. No active exploitation has been identified (no CISA KEV listing), and SSVC rates exploitation as none and automatability as no, reducing immediate operational urgency.

Authenticated path traversal in Winter CMS's LESS compilation pipeline allows backend users holding any of four specific permissions to exfiltrate arbitrary files readable by the PHP process - most critically the application .env file containing APP_KEY and database credentials. The vulnerability affects Winter CMS versions through 1.2.12 via four injection sinks: Brand Settings, Editor Settings, Mail Brand Settings colour fields, and theme CSS assets compiled by CombineAssets. No public exploit identified at time of analysis and no active exploitation confirmed, but confidentiality impact is high given .env disclosure enables full application key compromise.

Arbitrary file deletion in Laravel Backpack CRUD (all 5.x, 6.x < 6.8.12, 7.x < 7.0.35) allows any authenticated low-privilege user - such as a content editor - to delete files outside the scope of the record they are editing by injecting arbitrary disk-relative paths into the `clear_<attr>[]` request parameter. The root cause is that `HasUploadFields::uploadMultipleFilesToDisk` passes attacker-supplied paths directly to `Storage::disk()->delete()` without intersecting them against the filenames actually stored in the database for that record. No confidentiality impact exists (files cannot be read), but an attacker can destroy any file reachable under the configured storage disk root, including other records' attachments and shared operational assets. No public exploit or KEV listing has been identified at time of analysis.

Path traversal in Cesanta Mongoose's SSI processing allows an authenticated network attacker to read arbitrary files accessible to the Mongoose process by embedding directory traversal sequences in #include file or #include virtual SSI directives. The mg_ssi() function in src/ssi.c constructs filesystem paths from directive arguments without invoking the existing mg_path_is_sane() validation, bypassing the only guard against traversal. Exploitation is constrained to deployments compiled with MG_ENABLE_SSI and a configured ssi_pattern; no public exploit has been identified at time of analysis.

Path traversal during backup restore in Velero (vmware-tanzu/velero) allows an attacker who has compromised the object storage backend to overwrite arbitrary files on the Velero pod filesystem by uploading a malicious tarball containing filenames with directory traversal sequences. Targeted files include /etc/cron.d/ entries (enabling code execution within the pod), ~/.ssh/authorized_keys (enabling persistent SSH access), and ~/.kube/config (enabling full Kubernetes cluster credential theft). No patch had been released at the time of advisory publication, though fix version 1.18.1 is indicated in package metadata, suggesting the fix was released shortly after disclosure. No public exploit code or CISA KEV listing identified at time of analysis.

Path traversal in VictoriaMetrics vmrestore (prior to versions 1.122.25, 1.136.12, and 1.146.0) allows an attacker who controls or can modify a remote backup source - S3, GCS, Azure Blob Storage, or equivalent - to plant dot-dot sequences in object names, causing vmrestore to write restored files outside the configured -storageDataPath directory when an operator executes a restore operation. The CVSS Scope Changed metric (S:C) reflects that successful exploitation reaches beyond the vmrestore process boundary to the broader host filesystem, enabling potential overwrite of binaries, configuration, or credentials within the OS permissions of the process. Vendor-released patches are available across three maintained branches; no active exploitation has been identified at time of analysis.

Remote code execution in Heimdall Data Database Proxy enables authenticated high-privilege attackers to run arbitrary code as root via a directory traversal flaw in the uploadJar method. The vulnerability, tracked as ZDI-CAN-28603 and published by Zero Day Initiative as ZDI-26-479, stems from the absence of proper path validation on user-supplied input before use in file operations, allowing arbitrary JAR placement on the underlying filesystem. No public exploit code and no CISA KEV listing are identified at time of analysis; exploitation is gated behind administrative authentication.

Path traversal in the Banks Python prompt-template library (all versions prior to 2.4.5) allows a low-privileged attacker to write arbitrary bytes to attacker-chosen filesystem paths accessible to the application process. DirectoryPromptRegistry.set() in directory.py constructs on-disk paths by directly interpolating unvalidated Prompt.name and Prompt.version values - enabling relative sequences like ../victim/foo or absolute paths to escape the configured registry root. The poisoned path persists in index.json and is reconstructed on subsequent registry loads, meaning exploitation survives application restarts. No public exploit or CISA KEV listing exists at time of analysis; a vendor-released patch is available as version 2.4.5.

Arbitrary file read in Apache InLong 2.0.0 through 2.3.x exposes the Agent host filesystem to unauthenticated remote attackers via a relative path traversal flaw. The CVSS vector AV:N/AC:L/PR:N/UI:N confirms exploitation requires no credentials or user interaction, making any network-exposed InLong Agent endpoint a direct confidentiality risk. No public exploit code and no CISA KEV listing have been identified at time of analysis; EPSS sits at 0.21% (12th percentile), indicating low observed exploitation probability despite the high base score.

Broken access control in Apache InLong's manager component exposes Data Node management endpoints to any authenticated user, regardless of their assigned role or privilege level. Versions 2.0.0 through 2.3.x are affected, allowing any valid manager account holder to create, modify, or delete Data Node definitions that underpin the platform's data pipeline infrastructure. The CVSS 8.1 High rating reflects high integrity and availability impact; no public exploit or CISA KEV listing exists at time of analysis.

Missing authorization enforcement in Apache InLong's StreamSource component allows any authenticated user - regardless of role - to logically delete all stream sources across the platform. Versions 2.0.0 through 2.3.x are affected; the root cause is CWE-552, where the StreamSource API performs no access-control check before executing the delete operation. No public exploit code is currently known and the vulnerability is absent from CISA KEV, but the extremely low exploitation barrier - a single valid account - makes this a serious risk for any multi-tenant or shared InLong deployment.

Unauthenticated file read in Handlebars.java's Spring MVC integration module (all versions prior to 4.5.3) allows remote attackers to retrieve arbitrary files accessible to the JVM process. The HandlebarsViewResolver passes attacker-controlled view names to handlebars.compile() without path-containment validation, and a file: or classpath: URL with a trailing # fragment delimiter causes the appended .hbs suffix to be silently discarded during resource resolution, bypassing the intended extension check. No active exploitation is confirmed (no CISA KEV listing) and no public POC has been identified at time of analysis, but the CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N) reflects meaningful risk for any deployment with user-influenced view name routing.

Path traversal in DigiDoc4 (versions 4.0.0 through 4.10.x) enables arbitrary filesystem writes when a user opens a specially crafted ASiC container file. The underlying libdigidocpp library parsed `full-path` entries in container manifests without validating traversal sequences such as `..`, allowing embedded files to be extracted outside the intended directory. No public exploit has been identified and no CISA KEV listing exists; the CVSS 4.0 score of 8.4 reflects high local confidentiality and integrity impact contingent on active user interaction.

Path traversal in ATutor's error log viewer grants authenticated administrators read access to arbitrary files outside the intended logs directory, up to the web server process's permission boundary. Only version 2.2.4 has been confirmed vulnerable by CERT.pl, though other versions may also be affected. No patch will be issued - the product is end-of-life - making migration or decommissioning the only durable remediation.

Remote code execution in ATutor 2.2.4 is achievable by any authenticated instructor through a path traversal flaw in the ZIP extraction functionality. An attacker uploads a crafted ZIP archive containing a malicious .phtml file at a directory-traversing path, causing the file to be written into the web root and executed with web server process privileges. No patch exists and none is forthcoming - ATutor is end-of-life - meaning affected deployments face a permanent, unmitigated RCE exposure; no public exploit code has been identified at time of analysis.

Path traversal in ATutor 2.2.4 enables an authenticated low-privilege user to read files belonging to other course directories when the AT_FORCE_GET_FILE configuration option is active, leaking file contents and exposing filesystem structure. The product is end-of-life with no vendor-released patch, making remediation dependent entirely on compensating controls or decommissioning. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.

Remote code execution in n8n workflow automation platform (versions before 2.33.4 and 2.34.x before 2.34.1) arises from a path traversal flaw in the @n8n/workflow-sdk MCP node-schema loader. An authenticated user holding global:member privileges can supply a crafted node type string containing path-traversal sequences, causing the loader to resolve and execute an arbitrary file on the server filesystem as a Node.js module within the n8n main process. No public exploit has been identified at time of analysis and the vulnerability is not in the CISA KEV catalog, but the low privilege requirement and straightforward exploitability make this a high-priority patch for all self-hosted n8n deployments.

Zip-slip path traversal in Frauscher FDS 102 enables a high-privileged remote attacker to overwrite arbitrary files on the server and achieve full system compromise. By uploading a specially crafted ZIP archive containing entries with directory traversal sequences (e.g., ../../etc/cron.d/backdoor), an authenticated attacker can escape the intended extraction directory and plant executable content in sensitive filesystem locations. No public exploit code or active exploitation has been identified at time of analysis, but the direct path from file write to code execution makes this a critical post-authentication escalation risk in industrial environments.

Direct HTTP access to an exposed SQL database backup file in code-projects Login Registration System 1.0 allows unauthenticated remote attackers to download the raw database dump at /loginsystem/database/login_registration_system.sql, disclosing user credentials, schema details, and any sensitive data stored in the application database. This is a CWE-552 file exposure defect - the backup artifact is stored within the web-accessible document root with no access controls. No exploitation beyond a standard HTTP GET request is required. A public proof-of-concept exploit exists; no KEV listing at time of analysis.

Arbitrary file read, write, and Python code execution in Agno's PythonTools (agno.tools.python) exposes any file accessible to the agent process via path traversal sequences injected into the file_name argument of read_file, save_to_file, or run_python_file. The root cause is use of Path.joinpath() without resolving or validating the resulting path against the intended base_dir boundary, enabling escape via sequences such as '../../../../../../etc/passwd'. No public exploit has been identified at time of analysis, but the attack is trivially constructible and can be delivered through direct tool invocation or prompt injection embedded in agent-processed content, giving any untrusted input source a path to OS-level code execution within the agent process.

Path traversal in Splunk SOAR below 8.6.0 enables users holding the OnPrem Broker role to write files to arbitrary locations outside the designated Automation Broker log directory. The flaw stems from the log upload endpoint accepting crafted filenames without adequate sanitization, allowing directory traversal sequences to escape the intended write boundary. No public exploit has been identified and no active exploitation is confirmed; the CVSS score of 2.7 (Low) accurately reflects the high privilege prerequisite and the limited, integrity-only impact.

Path traversal in Splunk SOAR's Universal Forwarder credentials-package extraction allows an authenticated Administrator to write files to arbitrary locations on the underlying host filesystem. Affecting all On-premises versions below 8.6.0, the flaw stems from the archive extraction workflow accepting member paths containing directory traversal sequences without first verifying each member's resolved destination. No public exploit or CISA KEV listing exists at time of analysis; however, the Integrity:High and Availability:High CVSS impact ratings indicate that a malicious archive could overwrite system-level files, enabling persistence or privilege escalation beyond SOAR's own permission boundary.

Path traversal during app installation in Splunk SOAR On-premises below version 8.6.0 allows an authenticated user holding app-install privileges to write files outside the intended temporary extraction directory. The archive extraction routine fails to validate that file paths within an uploaded archive remain within the designated staging directory, enabling a classic Zip Slip attack that can overwrite arbitrary files on the host. No public exploit has been identified at time of analysis, and exploitation is constrained by the high-privilege prerequisite (PR:H); a vendor-released patch is available in version 8.6.0.

Arbitrary code execution in Splunk SOAR (On-premises) versions below 8.6.0 is reachable by any authenticated user regardless of role assignment, via a crafted file path submitted to the REST API. The REST API endpoint neither enforces role-based access control nor restricts the user-supplied path to the intended temporary directory, enabling path traversal (CWE-22) that culminates in code execution on the SOAR server. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; however, the low privilege barrier - any valid account, zero roles required - meaningfully elevates real-world risk in environments where SOAR accounts are broadly provisioned.

Path traversal in Splunk Enterprise exposes JavaScript files outside the Splunk Web static directory to unauthenticated remote attackers across four active release branches. Splunk Web fails to enforce boundaries on static file requests, allowing directory traversal reads without any credentials. No public exploit code has been identified at time of analysis and this vulnerability is not listed in the CISA KEV catalog, but the trivially low attack complexity (AC:L, PR:N, UI:N) means exploitation requires no special tooling.

Arbitrary code execution in IBM OpenBMC FW1060.00 through FW1060.80 is achievable via a path traversal flaw (CWE-22) in the BMC firmware update process, resulting in full confidentiality, integrity, and availability compromise of the baseboard management controller. Exploitation is constrained to authenticated administrators with adjacent network access to the BMC management interface, substantially limiting the real-world attack surface despite the high CIA impact. No public exploit code and no CISA KEV listing have been identified at time of analysis.

Path traversal in BuildKit prior to v0.31.2 enables an authenticated API client to escape the daemon's controlled state directory by submitting a crafted upload request containing traversal sequences. Affected parties include any deployment where multiple principals share BuildKit API access - such as multi-tenant CI/CD infrastructure or shared Docker build environments. The vulnerability grants a write primitive to arbitrary host filesystem locations, posing high integrity and availability risk; no public exploit or CISA KEV listing has been identified at time of analysis.

Path traversal in RuoYi-Vue up to 3.9.2 allows authenticated low-privilege users to read arbitrary files from the server filesystem by manipulating the `fileName` or `resource` parameters of the Common Download Endpoint in `CommonController.java`. A publicly available exploit has been disclosed via GitHub issue, but no patch has been released and the maintainer has not responded to the disclosure. No CISA KEV listing is present, so confirmed active exploitation at scale is unverified, though the public POC and low attack complexity make opportunistic exploitation by authenticated insiders or compromised accounts a realistic near-term risk.

Path traversal in IBM AIX 7.2 and 7.3 and IBM PowerVM VIOS 4.1 exposes sensitive files to remote, unauthenticated attackers over the network. The flaw (CWE-22) allows directory traversal sequences to escape an intended path boundary, enabling read access to files that should not be externally accessible. No active exploitation has been confirmed by CISA KEV, and no public exploit code has been identified at time of analysis.

Path traversal in @logto/tunnel (versions <= 0.3.8) exposes arbitrary file read to any network peer that can reach the tunnel port when the --experience-path flag is active. The Node.js static file proxy passes request.url directly into path.join(staticPath, request.url) followed by fs.open without URL normalization or containment checks, allowing ../ sequences to escape the configured static directory. A working proof-of-concept is publicly documented in GHSA-rxjr-6c9q-h67x; no active exploitation is confirmed in CISA KEV as of the analysis date, and the vendor-released fix is version 0.3.9.

External $ref resolution in Orval prior to version 8.22.0 allows server-side request forgery and path traversal against the developer or CI host that processes an attacker-controlled OpenAPI or Swagger specification. Any OpenAPI description containing crafted $ref values - pointing to internal HTTP services, cloud metadata endpoints such as the AWS IMDSv1 endpoint, or absolute local file paths - is resolved unconditionally by Orval's import-specs.ts loader with no allowlist or directory confinement. Beyond data exfiltration, untrusted remote schemas are inlined directly into the generated TypeScript client, potentially introducing malicious type definitions into downstream codebases. No active exploitation is confirmed (not in CISA KEV), but the network-delivery path with no authentication requirement makes this a meaningful supply chain risk for teams that process third-party OpenAPI descriptions.

Arbitrary file deletion on a Wazuh manager via the cluster synchronization protocol allows a cluster-authenticated attacker to destroy critical files including ossec.conf, jwt_secret.json, and TLS certificates, effectively disabling the manager or invalidating all API authentication tokens. The flaw spans Wazuh 4.0.0 through 4.14.5 and the 5.0.0-beta2 pre-release, rooted in missing path canonicalization inside the cluster file-receive cleanup handler. No public exploit or active exploitation has been identified at time of analysis; however, CVSS 4.0 rates the vulnerable-system impact as High across confidentiality, integrity, and availability, making this a high-priority patch for any clustered Wazuh deployment.

Path-traversal-driven root code execution affects the Wazuh security platform's cluster synchronization layer in versions 4.0.0 through 4.14.5 and the 5.0.0-beta line up to 5.0.0-beta3. A malicious or compromised cluster peer that possesses the shared Fernet key can smuggle directory-traversal sequences through merge_type/name values or a merged-file header, causing the master node to write attacker-controlled files (e.g. /var/ossec/etc/ossec.conf) outside the intended cluster item directory; overwriting ossec.conf lets the attacker define root-executed commands that fire when Wazuh services reload. No public exploit has been identified at time of analysis, and the issue is not in CISA KEV; the vendor fix landed in 4.14.6 and 5.0.0-beta3.

CPython's tarfile module on POSIX platforms creates empty directories outside the intended extraction destination when processing archive members whose names temporarily escape and re-enter it, such as '../evil/../dest/sub/file'. The extraction filters ('tar' and 'data') validate the resolved path - which correctly resolves to inside the destination - but create intermediate directories from the raw member name as given, allowing filesystem pollution beyond the extraction boundary. File contents are never placed outside the destination, and no public exploit has been identified at time of analysis; the PSF advisory confirms the limited scope.

Path traversal in OpenEMR's EDI archive restore function before version 8.3.0 enables authenticated users with EOB Data Entry permissions to enumerate arbitrary filesystem paths on the server via a differential response oracle. The unsanitized `archrestore_sel` POST parameter is passed directly to the archive restore handler, which checks the resolved path against the filesystem and returns distinct messages depending on whether the path exists - leaking file existence without disclosing file contents. No public exploit has been identified at time of analysis, and a vendor-released patch is available in OpenEMR 8.3.0.

Unauthenticated remote code execution in sgoudelis Ground Station before 0.4.13 arises from chaining a path-traversal file write with an insecure logging-config reload. The unauthenticated save-waterfall-snapshot Socket.IO command lets a remote attacker write attacker-controlled bytes anywhere on disk, then use the equally unauthenticated update-app-config and restart_service commands to load a malicious logging YAML that executes a Python callable factory with service privileges (or forces a persistent crash loop). Rated CVSS 9.8; no public exploit identified at time of analysis, though the fixing commit and advisory describe the full exploit chain.

Unauthenticated path traversal in Ground Station before v0.4.13 allows remote attackers to read arbitrary JSON-parseable files outside the intended recordings directory via the Socket.IO configure-sdr command. The sigmf-playback SDR type accepts an unsanitized recordingPath parameter that is stored verbatim and later opened by the sigmfprobe backend, enabling absolute-path or directory-traversal payloads to escape backend/data/recordings and return file contents to the caller. No public exploit has been identified at time of analysis; a vendor-released patch exists as of version 0.4.13.

Arbitrary file upload and deletion in the J-BusinessDirectory extension for Joomla (versions before 6.2.3) lets remote attackers write or remove files anywhere in the component's site and administrator directory trees, enabling web shell deployment and full site compromise. The flaw combines a client-controlled storage root (_path_type), absent path-containment checks, a weak file-extension filter, and a missing CSRF token on the upload/remove handlers. Rated CVSS 4.0 10.0 (critical); there is no public exploit identified at time of analysis and it is not listed in CISA KEV.

Unauthenticated remote file overwrite in IBM AIX 7.2/7.3 and PowerVM VIOS 4.1 is possible via the nimesis registration service, which fails to sanitize path traversal sequences in client-supplied input. An attacker with network access to the nimesis service can write arbitrary content to locations outside the intended directory, potentially overwriting sensitive system files such as cron jobs, init scripts, or authentication databases. No public exploit or active exploitation has been identified at time of analysis, though the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates this is straightforwardly exploitable without authentication.

Path traversal in GitPython before 3.1.58 allows remote attackers who control a Git repository to create fully initialized, attacker-controlled Git repositories at arbitrary filesystem paths outside the intended clone directory. GitPython's independent submodule implementation reads submodule names from .gitmodules without any validation - a check that core Git added years ago in response to CVE-2018-11235 - and passes the raw, traversal-containing name directly to os.makedirs() and git clone. A proof-of-concept with Docker-based reproduction is publicly documented in GHSA-hmq2-w58f-27jc; no CISA KEV listing is present at time of analysis, indicating exploitation is not yet confirmed as widespread.

Path traversal in Dell OpenManage Enterprise prior to version 4.7.0 allows a remote low-privileged attacker to read files outside the intended directory scope, resulting in information exposure. The vulnerability is classified under CWE-22 and carries a CVSS 3.1 base score of 6.5 (Medium), with high confidentiality impact and no integrity or availability impact. No public exploit code or active exploitation has been identified at time of analysis.

Arbitrary file write in the W3 Total Cache WordPress plugin before 2.10.5 lets unauthenticated remote attackers overwrite any existing file inside or outside the web root by manipulating the request path used to construct cache file names. Because the plugin builds cache filenames from an unvalidated path, attackers can clobber security-critical files such as Apache .htaccess, breaking the site and stripping hardening rules that other controls depend on. No public exploit identified at time of analysis and EPSS is low (0.18%), but SSVC rates technical impact as total and the flaw is automatable, so priority is high despite the current lack of observed exploitation.

Unauthenticated path traversal in the Simple File List WordPress plugin (versions through 6.3.11) exposes an unvalidated file-move endpoint accessible without authentication, enabling arbitrary server file reads and displacement of critical WordPress files outside the web root. Remote attackers can exfiltrate sensitive data such as wp-config.php database credentials and secret keys, and can displace core WordPress files to cause site failure or enable site takeover. No public exploit code has been identified at time of analysis, but the CISA SSVC framework rates the attack as automatable with no privileges required, elevating real-world risk despite a low current EPSS score.

Arbitrary file deletion in the Atarim AI Agency for WordPress plugin (all versions through 5.1.1) allows authenticated attackers holding author-level credentials to delete any file on the underlying server via a chained directory traversal attack, with a direct path to remote code execution. The exploit chain poisons WordPress attachment metadata with a traversal path and then triggers the plugin's media replacement workflow to resolve and unlink the attacker-chosen target file. No public exploit has been identified at time of analysis, but the Wordfence advisory fully documents the two-step chain against verified source code, making independent reproduction straightforward for a moderately skilled attacker.

Arbitrary root-readable file disclosure in Linuxfabrik Monitoring Plugins prior to 7.0.0 allows a local attacker controlling the monitoring account to exfiltrate sensitive files such as /etc/shadow by supplying a crafted --filename path to the logfile check plugin, which executes as root via the shipped sudoers allowlist without confining the resolved path to /var/log. The same path-traversal flaw extends to the mysql-logfile and openvpn-client-list plugins. No public exploit code or CISA KEV listing has been identified at time of analysis, but the attack is straightforward and requires only monitoring-account-level access.

Path traversal in Streambert's Electron desktop app before version 2.6.0 allows a compromised renderer process to direct the privileged main process to create directories, write renderer-controlled JSON data, and delete files at arbitrary filesystem locations outside the intended backup directory. The vulnerable `perform-scheduled-backup` IPC handler in `src/ipc/storage.js` accepts `settings.path` from the renderer without validating it against an authorized backup location, enabling traversal via absolute paths or `../../`-style sequences. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the high integrity and availability impact across both the vulnerable system and subsequent systems is reflected in the CVSS 4.0 score of 8.4.

Path traversal in Streambert (versions prior to 2.5.0) allows a compromised Electron renderer process to abuse the run-download IPC channel to copy arbitrary files readable by the Streambert process into attacker-controlled locations, and to overwrite existing writable files on the host system. The downloadSubtitleFile utility in src/ipc/downloads.js accepts renderer-supplied file: URIs and destination paths without sanitization, passing them directly to fs.copyFileSync - crossing the Electron IPC boundary without restriction. No public exploit is identified at time of analysis, but the CWE-22 path traversal root cause is well-understood and the vendor-released patch is available in version 2.5.0.

Path traversal in 4gaBoards before version 3.3.8 allows authenticated project managers to read and then delete arbitrary files accessible to the server process through a crafted filename parameter in the export download endpoint. The vulnerability in `server/api/controllers/boards/download.js` passes unsanitized user input directly to `path.join()` without containment validation, enabling escape from the intended `private/exports/<user_id>/` directory. A compounding defect in the stream close handler passes the same traversal path to `fs.unlink()`, meaning each exploited download request also destroys the targeted file - combining exfiltration with irreversible data loss in a single HTTP request. No public exploit has been identified and the vulnerability is not listed in the CISA KEV catalog.

Path traversal in Confidential Containers guest-components (image-rs) versions 0.16.0 through 0.19.x allows a workload owner to create hardlinks outside the OCI layer destination directory and into arbitrary absolute paths within the pod virtual machine. The root cause is Rust's standard library behavior where `Path::join()` silently discards the base path when the right-hand operand is absolute, allowing a crafted tar entry to bypass directory confinement in `try_hardlink_fallback()`. While this does not cross the image trust boundary - the workload owner already controls trusted image content - it enables escape into pod VM capabilities and potential attestation abuse; no public exploit code has been identified at time of analysis.