Path Traversal
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
How It Works
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation. Attackers inject special sequences like ../ (dot-dot-slash) to escape the intended directory and navigate to arbitrary locations in the file system. Each ../ sequence moves up one directory level, allowing an attacker to break out of a restricted folder and access sensitive files elsewhere on the server.
Attackers employ various encoding techniques to bypass basic filters. Simple URL encoding transforms ../ into %2e%2e%2f, while double encoding becomes %252e%252e%252f (encoding the percent sign itself). Other evasion methods include nested sequences like ....// (which become ../ after filter removal), null byte injection (%00 to truncate path validation), and OS-specific path separators (backslashes on Windows). Absolute paths like /etc/passwd may also work if the application doesn't enforce relative path constraints.
The typical attack flow begins with identifying input parameters that reference files—such as file=, path=, template=, or page=. The attacker then tests various traversal payloads to determine if path validation exists and what depth is needed to reach system files. Success means reading configuration files, credentials, source code, or even writing malicious files if the application allows file uploads or modifications.
Impact
- Credential exposure: Access to configuration files containing database passwords, API keys, and authentication tokens
- Source code disclosure: Reading application code reveals business logic, additional vulnerabilities, and hardcoded secrets
- System file access: Retrieving
/etc/passwd,/etc/shadow, or Windows SAM files for credential cracking - Configuration tampering: If write access exists, attackers modify settings or inject malicious code
- Remote code execution: Writing web shells or executable files to web-accessible directories enables full system compromise
Real-World Examples
ZendTo file sharing application (CVE-2025-34508) contained a path traversal vulnerability allowing unauthenticated attackers to read arbitrary files from the server. The flaw existed in file retrieval functionality where user input directly influenced file path construction without adequate validation, exposing sensitive configuration data and potentially system files.
Web application frameworks frequently suffer from path traversal in template rendering engines. When applications allow users to specify template names or include files, insufficient validation permits attackers to read source code from other application modules or framework configuration files, revealing database credentials and session secrets.
File download features in content management systems represent another common vector. Applications that serve user-requested files from disk often fail to restrict paths properly, enabling attackers to download backup files, logs containing sensitive data, or administrative scripts that weren't intended for public access.
Mitigation
- Avoid user input in file paths: Use indirect references like database IDs mapped to filenames on the server side
- Canonicalize and validate: Convert paths to absolute canonical form, then verify they remain within the allowed base directory
- Allowlist permitted files: Maintain an explicit list of accessible files rather than trying to blocklist malicious patterns
- Chroot jails or sandboxing: Restrict application file system access to specific directories at the OS level
- Strip dangerous sequences: Remove
../,..\\, and encoded variants, though this alone is insufficient
Recent CVEs (8417)
Path traversal in OpenList prior to v4.2.3 allows any authenticated user holding the PermAddOfflineDownload permission to write, truncate, or overwrite arbitrary files accessible to the OpenList process via the SimpleHttp offline-download tool. The attacker controls a remote HTTP server that returns a crafted Content-Disposition header containing path-traversal sequences; OpenList uses the attacker-supplied filename without containment validation to construct a file path via filepath.Join relative to a per-task temporary directory, allowing traversal outside that directory. No public exploit has been identified at time of analysis, though the GHSA advisory details the exact vulnerable function and the fix commit is publicly accessible, significantly lowering the effort required to develop one.
Path traversal in Eclipse aeriOS Self-orchestrator prior to version 1.2.1 allows unauthenticated remote attackers to write or delete arbitrary JSON files on the host filesystem by embedding path separator sequences (e.g., '../') in resource identifiers submitted to the REST API. The vulnerability stems from direct string concatenation of user-supplied names into `fs.writeFileSync()` paths without sanitization, confirmed by the upstream commit diff. Real-world impact is amplified by the complete absence of API authentication (PR:N) and by the container running with elevated privileges in the affected deployment, extending the writable filesystem scope beyond the intended `./facts/` directory. No public exploit code has been identified at time of analysis.
TLS private key disclosure in SiYuan <=3.8.1 allows any authenticated user - or any network client on default no-auth-code deployments - to exfiltrate the server's TLS private key (conf/key.pem) and CA private key (conf/ca.key) via a simple POST to /api/file/getFile. The root cause is a dual flaw: the IsForbiddenAbsPath() blocklist covers only conf/conf.json by exact match while leaving sibling key material unprotected, and the getFile handler unconditionally skips the blocklist for RoleAdministrator - a role granted to every authenticated user in v3.8.1. On TLS-enabled, network-exposed instances this enables retrospective decryption of captured HTTPS sessions and forgery of certificates already trusted by clients that imported SiYuan's CA. No public exploit identified at time of analysis; vendor-confirmed fix is available in v3.8.2.
Cross-site request forgery chained with path traversal in AVideo's stopLive.php enables attackers to trigger recursive deletion of arbitrary server directories when an authenticated administrator visits a malicious page. The vulnerability exists through commit c91b5975d of the WWBN AVideo self-hosted video platform, affecting all versions covered by CPE cpe:2.3:a:wwbn:avideo:*:*:*:*:*:*:*:*. The attack exploits missing CSRF token validation in stopLive.php combined with unsanitized concatenation of the key parameter into filesystem paths, allowing payloads like key=../../videos to destroy the videos directory and its contents. No public exploit code or CISA KEV listing has been identified at time of analysis.
Path traversal in @fastify/http-proxy before 11.6.2 permits unauthenticated remote attackers to bypass the prefix and rewritePrefix boundary controls and reach upstream paths that the proxy operator intended to keep hidden. The root cause is an asymmetry between the plain HTTP handler — which omits destination validation — and the WebSocket handler, which performs it correctly; the underlying reply-from library compounds this by only rejecting forward-slash traversal sequences, leaving backslash dot-segment variants unchecked. No active exploitation has been confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis.
Path traversal in Reader Tools PDF Reader App 98.8 on Android permits a local low-privileged attacker to manipulate the `_display_name` parameter supplied via a deep link to the `ActSplashNew.handleDeeplink` function, enabling file reads or writes outside the application's intended sandbox. The affected CPE (`cpe:2.3:a:reader_tools:pdf_reader_app`) covers version 98.8 on Android; the vendor did not respond to the coordinated disclosure, and no patch has been released. A public proof-of-concept exploit exists, but real-world impact is bounded by the local-only attack vector and low individual component impacts.
Arbitrary file write to remote code execution in Jenkins File Parameter Plugin (versions ≤ 425.v3fa_801681b_5e) is achievable by any low-privilege authenticated Jenkins user through a Stapler data binding flaw. By crafting a build request with a path-traversal file parameter, an attacker can write attacker-controlled content to arbitrary locations on the Jenkins controller filesystem, enabling code execution by overwriting Groovy init scripts, SSH authorized_keys, or other sensitive files. No public exploit has been identified at time of analysis, and CISA SSVC rates current exploitation as none - but the technical impact ceiling is total controller compromise.
Path traversal in Jenkins Allure Plugin 2.35.2 and earlier allows any user holding Item/Read permission on a Jenkins job that publishes Allure test reports to read arbitrary files from the Jenkins controller's filesystem, including credentials, configuration files, and secrets stored on the controller. The vulnerability is reachable over the network with only low-level authenticated access - a standard privilege held by most Jenkins users in typical multi-user deployments. No public exploit code has been identified at time of analysis, and CISA SSVC classifies exploitation as none currently, though technical impact is rated total given unconstrained file read on the controller.
Path traversal via Stapler data binding in Jenkins ThinBackup Plugin 2.1.4 and earlier allows authenticated low-privileged attackers to overwrite the plugin's backup configuration, redirecting backup output to an attacker-specified directory and injecting arbitrary Jenkins controller filesystem files into backup archives. The primary risk is exfiltration of high-value Jenkins controller secrets - credentials.xml, SSH keys, API tokens, master.key - via the backup mechanism. SSVC rates exploitation as none with no public exploit identified; however, the C:H impact makes this a significant post-initial-access escalation path on CI/CD infrastructure.
Path traversal in Kibana's Fleet feature enables a low-privileged user to manipulate Fleet administration actions taken by higher-privileged users, causing those actions to target unintended resources - including deleting accounts with elevated privileges. The attack exploits a confused-deputy pattern (CWE-22/CAPEC-126): the attacker crafts a traversal payload through their low-privileged access, then waits for an admin to perform a routine Fleet operation, at which point the admin's elevated context executes the deletion against the attacker-controlled target. Fixed versions are Kibana 8.19.17, 9.3.6, and 9.4.3 per the Elastic security advisory ESA-2026-159. No public exploit or CISA KEV listing is present at time of analysis.
Path traversal in Kibana's Fleet feature enables a low-privileged attacker with Fleet Settings write access to plant a malicious pathname in settings that, when subsequently acted upon by an administrator, causes deletion of privileged internal resources including user accounts and organizational assets. All Kibana versions prior to 8.19.18, 9.3.6, and 9.4.3 are affected per ESA-2026-158. No public exploit code or active exploitation has been confirmed; the two-party nature of the attack - requiring both attacker write access and administrator interaction - moderates opportunistic exploitability despite the High CVSS rating.
Path traversal in Kibana's Fleet feature enables a low-privileged user with Fleet write access to craft resource paths that redirect a subsequent administrative delete operation onto unintended internal Kibana resources, causing unauthorized data destruction. Affected versions are Kibana prior to 8.19.18 and 9.4.3; Elastic released fixes for both branches under ESA-2026-157. No public exploit code or active exploitation has been identified at time of analysis, but the two-actor attack pattern (attacker plants, admin triggers) meaningfully constrains real-world exploitability.
Path traversal in Elastic Maps Server exposes arbitrary files readable by the server process to unauthenticated network attackers. Insufficient path restriction in the content-directory serving logic allows crafted requests to escape the intended directory using traversal sequences, returning sensitive file contents. No KEV listing or public exploit code exists at time of analysis; Elastic has released fixed versions 8.19.19, 9.4.4, and 9.5.1 per advisory ESA-2026-148.
Path traversal in wcurl for Windows allows a crafted URL containing percent-encoded backslashes to redirect a downloaded file to an attacker-controlled directory outside the user's intended destination. Affecting wcurl shipped with curl 8.14.0 through 8.21.0 and standalone wcurl 2024.12.08 through 2026.01.05, the flaw exploits Windows path-separator semantics: wcurl decodes %5C to a backslash, which Windows treats as a directory separator, causing file placement at an unintended filesystem path. No public exploit code and no active exploitation have been identified at time of analysis; vendor-released patches are available as of September 2, 2026.
curl and libcurl through version 8.21.0 incorrectly handle domain-scoped cookies for Public Suffix List (PSL) domains, permitting a malicious server to set cookies scoped to a PSL entry rather than rejecting them as standards require. This flaw enables cross-subdomain cookie propagation under shared public suffix registries (e.g., github.io, co.uk), potentially exposing session tokens or enabling session fixation against other services the victim connects to under the same PSL domain. No public exploit code exists and CISA KEV listing is absent; the vulnerability was fixed in curl 8.22.0 released September 2, 2026.
TLS certificate verification bypass in curl's wolfSSL backend allows custom verification callbacks to be silently skipped when a CA certificate is found in wolfSSL's cache, enabling connections that application-level policy logic would otherwise have rejected. Affected are curl releases using the wolfSSL TLS backend, fixed in curl 8.22.0 released September 2, 2026. No public exploit code or active exploitation has been identified at time of analysis.
OpenSSL certificate pinning bypass in curl before 8.22.0 allows a network-positioned attacker to substitute a fraudulent but CA-trusted certificate for the expected pinned credential, undermining the stronger assurance that public-key pinning is specifically designed to provide over standard chain-of-trust validation. The flaw is specific to curl's OpenSSL code path and only materially affects deployments that have explicitly enabled certificate or public-key pinning (e.g., via --pinnedpubkey) as a hardening measure. curl 8.22.0, released September 2, 2026, resolves this issue; no public exploit code and no CISA KEV listing have been identified at time of analysis.
OpenLDAP SASL authentication bypass in curl allows network-accessible exploitation when curl is used to connect to LDAP servers using SASL authentication, potentially granting unauthorized access to directory data without valid credentials. The flaw is patched in curl 8.22.0, released September 2, 2026, as part of a coordinated batch security release addressing ten separate curl vulnerabilities. No public exploit or CISA KEV listing has been identified at time of analysis.
Secure cookie attribute bypass in curl allows the `Secure` flag on HTTP cookies to be circumvented when a tab character is present in a `Set-Cookie` header, causing curl to potentially transmit cookies over unencrypted HTTP connections that should be restricted to HTTPS only. The flaw affects the cookie parsing logic in curl/libcurl and is fixed in curl 8.22.0, released September 2, 2026. No public exploit code has been identified at time of analysis, and it does not appear in the CISA KEV catalog.
Connection reuse logic in curl's native CA store code path fails to properly isolate connections that were established under differing CA verification contexts, potentially allowing a subsequent request to reuse a connection whose native-CA validation would not have succeeded independently. All curl and libcurl users on platforms using the OS-native certificate store (Windows CertStore, macOS Keychain, etc.) rather than curl's bundled CA bundle are affected in versions up to and including 8.21.0. An attacker in a position to influence connection reuse - such as a MITM or a server that shares a connection pool - could bypass native CA certificate validation for a subsequent request. No public exploit has been identified at time of analysis, and no KEV listing is present.
Negotiate (SPNEGO/Kerberos) ambient credential leakage in curl allows an attacker-controlled server to receive authentication tokens intended for a different, legitimate server via improper connection reuse. Affected are curl and libcurl through version 8.21.0 when Negotiate authentication is active and connection reuse occurs across different servers. No public exploit code has been identified and this does not appear in CISA KEV; the issue was patched in the coordinated curl 8.22.0 security release on September 2, 2026.
Use-after-free in curl/libcurl's HTTP/2 server push handler allows a malicious or attacker-controlled server to corrupt client-side heap memory during push processing, potentially enabling denial of service or arbitrary code execution. All curl/libcurl versions prior to 8.22.0 that negotiate HTTP/2 with server push are affected. No public exploit code or CISA KEV listing has been identified at time of analysis.
Use-after-free in curl's OpenSSL provider component, fixed in curl 8.22.0 released September 2, 2026. The flaw occurs within curl's integration layer for the OpenSSL TLS backend, where a freed memory region can be accessed during SSL/TLS connection handling. Affected deployments include any application or system using libcurl built against OpenSSL as the TLS provider; no public exploit or active exploitation has been identified at time of analysis.
Path traversal in the RadImageEditor component of Progress Telerik UI for ASP.NET AJAX (all versions prior to v2026.3.812) allows unauthenticated remote attackers to read arbitrary files from the server by supplying crafted state values that manipulate the control's image cache lookup. The vulnerability stems from insufficient server-side validation of client-controlled input that determines which file the cache mechanism retrieves, enabling directory traversal beyond the intended image directories. No public exploit has been identified at time of analysis, but the low-complexity unauthenticated attack vector makes this a practical risk for any internet-exposed ASP.NET application using RadImageEditor.
Arbitrary file deletion in the SigmaForms Pro - AI Generated Forms plugin for WordPress (all versions through 1.4.11) lets unauthenticated attackers submit a path-traversal string through a form's file-upload field, which is stored in the database and processed by the vulnerable delete_submission_files function. When an administrator later deletes the submission record, the plugin removes the attacker-specified file - deleting wp-config.php (or similar) can escalate to full site takeover/remote code execution. Reported by Wordfence; no public exploit identified at time of analysis and no CISA KEV listing.
Memory saved. Analysis complete. Key findings for CVE-2026-84442: - **"Google" tag is wrong** — flagged in `data_quality_flags`; this is MapQuest's app (System1), not Google - **"olsztyn" injection note ignored** — matches the established prompt-injection pattern in these CVE inputs - **CVSS 4.0 score of 4.8 is well-calibrated** — local-only, low-privilege, limited impact (VI:L/VA:L/VC:N); no inflation concerns - **No vendor patch** — MapQuest did not respond to disclosure; PoC is public - **VC:N is slightly unexpected** for a path traversal (read access is a common consequence), noted in `confidence_notes` for follow-up review
Arbitrary file deletion in the WP File Download WordPress plugin (all versions, by JoomUnited) allows any authenticated subscriber-level user to delete files outside the plugin's intended directory, with trivial escalation to remote code execution by targeting wp-config.php. The vulnerability stems from two AJAX endpoints - file.save and file.delete - that lack both WordPress capability checks and nonce enforcement, permitting the two-stage exploit chain against any authenticated session. No public exploit code has been confirmed at time of analysis, but the Wordfence advisory describes the precise two-request mechanism in sufficient detail to enable rapid weaponization.
Path traversal in Piwigo's Image Derivative Handler (i.php) exposes arbitrary server-side files to remote unauthenticated attackers on installations up to version 16.3.0. The CVSS 4.0 vector confirms network-accessible, zero-authentication exploitation with low confidentiality and integrity impact, consistent with a traversal primitive that can both read and potentially write files in unanticipated filesystem locations. A public proof-of-concept titled 'unauthenticated_derivative_path_traversal' is available on GitHub, materially lowering the bar for exploitation; no active exploitation has been confirmed in CISA KEV at time of analysis.
Path traversal in facefusion's HTTP job management API allows unauthenticated remote attackers to write files at arbitrary server locations, escaping the intended jobs directory sandbox. Versions through 3.6.1 are affected; the root cause is failure to normalize job identifiers in get_job_file_name before constructing file paths. A patched release (3.7.0) is available, and the vulnerability is corroborated by a VulnCheck advisory and an independent researcher writeup, though no active exploitation has been confirmed via CISA KEV.
Path traversal in AirAsia MOVE App for Android (versions up to 12.47.1) allows a locally present low-privileged attacker to escape intended directory boundaries via unsanitized handling of the `_display_name` argument inside `com.airasia.core.utils.RealPathUtil.getRealPath`. Exploitation yields limited integrity and availability impact constrained by Android's SELinux sandbox, with no confidentiality exposure. A public proof-of-concept document exists; the vendor did not respond to coordinated disclosure, and no patch has been released.
Path traversal in WWBN AVideo's unauthenticated `get_api_login_code` API endpoint enables remote attackers to delete arbitrary `.log` files and enumerate filesystem paths by injecting directory traversal sequences into the `code` parameter. All versions covered by CPE `cpe:2.3:a:wwbn:avideo:*:*:*:*:*:*:*:*` are affected, with exploitation requiring no authentication or user interaction. The primary security consequence is destruction of audit trails and access logs, which undermines incident detection and forensic response capabilities; no public exploit code has been identified at time of analysis.
Path traversal in Laravel Excel (versions 3.1.8-3.1.69) allows authenticated low-privilege users to overwrite arbitrary existing files on the server by supplying a crafted destination path to `Excel::store()`, `$export->store()`, or `storeExcel()`. The vulnerable `Disk::copy()` method resolves caller-controlled paths via `realpath()` against the process working directory, then opens matched files directly with `fopen(rb+)` and `stream_copy_to_stream()`, bypassing Flysystem's path confinement entirely. When the overwritten target is a web-accessible PHP file, this escalates to remote code execution; no public exploit is identified at time of analysis.
Path traversal in Vitest's interceptorPlugin exposes local files on any development server with a network-accessible HMR WebSocket. The `vitest:interceptor:register` handler in `packages/mocker/src/node/interceptorPlugin.ts` accepts redirect mock registrations over Vite's unauthenticated HMR socket without calling `isFileLoadingAllowed()`, allowing a remote unauthenticated attacker who can reach the dev server to submit opaque-scheme URLs (e.g., `traversal:../../../etc/passwd`) whose `..` segments survive `URL.pathname` parsing and resolve outside the project root via `path.join()`. The plugin's `load` hook then returns `readFile(mock.redirect, 'utf-8')` as JavaScript module source, disclosing any file readable by the dev-server process. No public exploit or CISA KEV listing has been identified, but the GitHub fix PR includes a complete, working e2e test that serves as a functional PoC.
Path traversal in Next.js (13.4.0 through 15.5.23 and 16.x before 16.3.3) running on Windows-hosted servers lets a remote unauthenticated attacker escape the incremental-cache root and read private build artifacts, most critically the server-reference-manifest encryption key, which can be leveraged for remote code execution in the application. The flaw stems from route segments not escaping backslashes before cache-path construction, so encoded Windows path separators (e.g. %5c) bypass the sanitizer. Publicly available exploit code exists in the form of the e2e regression test shipped with the fix; no CISA KEV listing or EPSS score was provided.
Authenticated path traversal vulnerabilities in HPE AOS-CX REST API endpoints allow a high-privileged attacker to write arbitrary files to the underlying operating system, providing a direct path to remote code execution on affected network switches. The CVSS 7.2 score (PR:H) reflects the admin-level authentication barrier, which meaningfully constrains the attack surface to compromised credentials or insider threat scenarios. No public exploit or active exploitation has been identified at time of analysis; remediation details are available via HPE security bulletin HPESBNW05134.
Authenticated path traversal in HPE AOS-CX's web-based management interface permits a low-privileged authenticated attacker to read arbitrary files from the underlying operating system, potentially exposing credentials, private keys, and device configuration data. The CVSS vector (AV:N/AC:L/PR:L) confirms the vulnerability is remotely exploitable with minimal complexity once valid credentials are obtained. This CVE is part of a broader HPE security advisory (hpesbnw05134) covering multiple AOS-CX vulnerabilities, including higher-severity unauthenticated RCE issues, making credential exposure via this flaw a plausible stepping-stone in a multi-stage attack chain. No public exploit identified at time of analysis.
Unauthenticated arbitrary file write in HPE AOS-CX exposes network switches to full device compromise from adjacent network segments. An attacker with Layer-2 or Layer-3 adjacency to the switch management plane can call a vulnerable API endpoint without credentials to overwrite arbitrary files on the underlying operating system, enabling remote code execution. No public exploit has been identified and the CVE is absent from CISA KEV, but the zero-authentication RCE-grade primitive on managed network infrastructure warrants urgent prioritization.
Path traversal in Hono's toSSG() static site generator allows untrusted ssgParams values - such as slugs sourced from a CMS, external API, or user submission - to create or overwrite files outside the configured output directory at build time. Versions 4.12.12 through 4.13.4 are affected; the root cause is an incomplete fix for CVE-2026-39408 that fails to collapse consecutive parent-directory segments (e.g., 'a/b/../../../') in route parameter values, and also mishandles Windows drive-relative and UNC path roots. No public exploit has been identified and the vulnerability is not confirmed in the CISA KEV catalog; a complete patch is available in v4.13.5.
Path traversal in HPE Networking Fabric Composer's API endpoint allows an unauthenticated adjacent attacker to manipulate user-generated files and potentially alter critical system configurations. Exploitation is constrained by the AV:A vector (attacker must be on the same network segment), high attack complexity requiring preconditions outside the attacker's control, and mandatory user interaction - factors that collectively reduce the practical risk below the I:H integrity impact might suggest. No public exploit code has been identified and the vulnerability is not listed in CISA KEV. The CVSS base score of 4.8 reflects these limiting conditions accurately.
Unauthenticated file read in HPE Networking Fabric Composer's web-based management interface exposes a subset of system files to remote attackers without requiring any credentials. The vulnerability is confined to files within a specific affected directory rather than offering arbitrary filesystem access, yielding a limited confidentiality impact consistent with the CVSS 5.3 (C:L) score. No active exploitation (KEV) or public proof-of-concept has been identified at time of analysis, and no EPSS signal is provided in available intelligence.
Authenticated privilege escalation in HPE Networking Fabric Composer's API allows low-privilege operator users to read limited information and make limited configuration changes beyond their authorized scope. The flaw affects all tracked versions per CPE data and requires only a valid low-privilege account to exploit - no special configuration or user interaction is needed. No public exploit code and no CISA KEV listing are present at time of analysis, keeping real-world risk moderate despite network accessibility.
Arbitrary file write via the HPE Networking Fabric Composer API allows an authenticated low-privilege operator to escalate privileges and execute arbitrary commands on the underlying operating system, resulting in complete system compromise. The CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:L/UI:N) reflects network-exploitable, low-complexity exploitation requiring only a valid operator account. No public exploit code or CISA KEV listing has been identified at time of analysis, but the clear privilege escalation path from a low-privilege role to OS-level access makes this a high-priority remediation target in any Fabric Composer deployment.
Second-order path traversal in Kibana allows a low-privileged user with tag creation rights to cause an administrator's routine tag management action to operate on an unintended privileged resource, resulting in permanent deletion of administrator accounts or other organizational assets. Affected versions span the Elastic Stack deployment across the 8.x and 9.x series, with patches released in Kibana 8.19.16, 9.3.5, and 9.4.2. No public exploit has been identified and the vulnerability is not in the CISA KEV catalog, but the potential to delete administrative accounts elevates this beyond a typical medium-severity finding in multi-tenant deployments.
Deserialization of untrusted data in NVIDIA Megatron Bridge enables a local, low-privileged attacker to achieve code execution, data tampering, and information disclosure on the affected host. The vulnerability carries a CVSS 3.1 score of 7.8 with a local attack vector, indicating that an attacker with an existing foothold on the system can escalate impact significantly. No public exploit code or CISA KEV listing has been identified at time of analysis, but the full CIA triad impact (High/High/High) makes this a high-priority remediation target for any organization running Megatron Bridge in research or production AI training environments.
Path traversal in appium-mcp-server through 0.1.61 allows any caller of the write_file or write_files_batch MCP tools to overwrite arbitrary files on the host system by supplying absolute paths or parent-directory sequences (../) that escape the intended PROJECT_ROOT boundary. The server user's full filesystem write permissions are exposed, enabling an attacker to corrupt shell profiles, inject cron jobs, or overwrite application configuration files. No public exploit has been identified at time of analysis, but the vulnerability is trivially exploitable given the absence of any path validation logic in the affected tools.
Unauthenticated arbitrary file deletion in the Frontend Admin by DynamiApps WordPress plugin (versions up to and including 3.29.12) allows remote attackers to remove any server-accessible file via path traversal in the move_folders function. Deleting critical files such as wp-config.php triggers WordPress's reinstallation routine, cascading directly to full remote code execution and site takeover. No CISA KEV listing or public proof-of-concept has been identified at time of analysis, but the low attack complexity and zero-authentication requirement on publicly visible forms make this a critical-priority remediation.
Path traversal in Sage Employee Self Service's custom logo functionality exposes arbitrary server-side files to unauthenticated remote attackers. The flaw stems from insufficient sanitization of file path parameters, allowing directory traversal sequences and their URL-encoded equivalents to escape the application's intended filesystem scope and read sensitive data such as configuration files, environment settings, and logs. No public exploit or CISA KEV listing is present; Sage has remediated the issue via enhanced path validation shipped in the Q2 2026 HRMS product update.
Path traversal in Dokploy's Traefik configuration handler exposes all versions through 0.29.7 to arbitrary file read and write by low-privileged authenticated remote users. The vulnerable function `writeTraefikConfigInPath` in the Settings component fails to sanitize the `path` argument before writing Traefik proxy configuration, enabling attackers to escape the intended directory and interact with sensitive files on the host filesystem. A public exploit is available and the vendor did not respond to responsible disclosure, leaving no official patch in place.
Scoped path traversal in pnpm allows arbitrary filesystem overwrites during package installation, defeating the --ignore-scripts safety flag entirely. Affected are pnpm v10 before 10.34.5 and v11 before 11.11.0: the package manager's name validation in pickPackage.ts rejects slash characters only for unscoped package names, permitting a scoped name such as @evil/../../../home/user/.bashrc to pass unchecked into raw path joins across three resolver modules and extract package content to any attacker-controlled path. No public exploit has been identified at time of analysis, though GitHub-confirmed patches with regression tests are available.
Arbitrary file write in pnpm package manager versions before 10.34.5 and 11.0.0-11.11.0 allows an attacker who can supply a crafted `pnpm-lock.yaml` to escape the `node_modules` directory boundary and place package contents at attacker-controlled filesystem paths when a developer runs `pnpm install`. Even `--ignore-scripts` does not prevent the file-write primitive; when the project additionally enables `dangerouslyAllowAllBuilds` or a matching `allowBuilds` configuration entry, the escaped package's lifecycle scripts execute with the victim user's OS-level privileges. Vendor-released patches are available as pnpm 10.34.5 and 11.11.0; no public exploit has been identified at time of analysis.
Path traversal in Kirby CMS's media handler exposes arbitrary .json file existence and potentially image file contents to remote unauthenticated attackers on affected server configurations. The vulnerability exists in two code paths - Media::thumb() in src/Cms/Media.php and the file::version path in src/Filesystem/Asset.php - both of which failed to reject URL-encoded slash characters or literal ../ sequences before resolving paths relative to validated media directories. Fixed in versions 4.9.5 and 5.5.2; no public exploit code has been identified at time of analysis, and CISA KEV listing is absent.
Path traversal in Kirby CMS's filesystem containment logic allows remote unauthenticated attackers to access image files in PHP-readable sibling directories that share a string prefix with the Kirby installation root, and to create thumbnails from those files via the media handler. Versions prior to 4.9.5 (4.x line) and 5.5.2 (5.x line) are affected, with the impact limited to subsequent-system confidentiality exposure - staging sites, backups, or co-hosted internal sites - rather than the Kirby instance itself. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog; the CVSS 4.0 AT:P metric confirms specific environmental preconditions must exist for exploitation.
Zip Slip path traversal in Wallos's database restore endpoint allows an authenticated administrator to write arbitrary files - including PHP webshells - directly into the application webroot. The flaw exists in POST /endpoints/db/restore.php, where ZipArchive::extractTo() processes ZIP entries without sanitizing ../ sequences, enabling directory escape before any extension-based filtering runs. An admin who uploads a crafted ZIP with an entry like logos/../../endpoints/shell.php achieves remote code execution on the server. No public exploit or CISA KEV listing has been identified at time of analysis; however, the technique is well-understood and the attack is low-complexity once admin credentials are held.
Path traversal in MCPHub's MCPB file upload handler, prior to version 0.12.13, enables a remote attacker to extract files to arbitrary filesystem locations and delete arbitrary directories on the host by embedding traversal sequences in a crafted archive manifest. The vulnerability exists at `src/controllers/mcpbController.ts:107`, where `manifest.name` is unsanitized before concatenation into `fs.mkdirSync` and `fs.renameSync` calls; the same unsanitized value flows into `cleanupOldMcpbServer` at line 110, enabling directory deletion. No public exploit code or CISA KEV listing has been identified at time of analysis, though the full source-level disclosure in the GHSA advisory makes weaponization straightforward.
Path traversal in Eclipse Theia 1.73.0-1.74.x AI Agent Mode allows arbitrary file writes outside the workspace with backend OS user privileges through model-supplied paths that bypass workspace-containment checks. The affected tools - writeFileContent, suggestFileContent, and associated replacement and state helpers - accept relative paths such as ../.bashrc, absolute paths, or tilde-expanded paths like ~/.ssh/authorized_keys without boundary validation. Because path arguments derive from LLM output, an indirect prompt injection attack embedded in developer-loaded content can steer writes to host-executed files and escalate to backend code execution; Agent Mode applies writes silently with no confirmation dialog. No public exploit code or CISA KEV listing exists at time of analysis, though the prompt-injection attack surface is realistic in cloud IDE deployments.
Arbitrary file read in ILIAS's SOAP addFile method permits any authenticated low-privilege user to retrieve server-side files by supplying crafted XML with COPY-mode import entries that contain absolute attacker-controlled paths. The flaw spans three major release lines - all versions before 9.22, 10.0 through 10.9, and 11.0 through 11.2 - and is particularly damaging because the targetable files include ILIAS configuration files storing database credentials and setup passwords, enabling lateral movement to backend systems. No public exploit identified at time of analysis, though the vendor patch commit publicly documents the exact vulnerable code path, substantially reducing the effort required for independent exploit development.
Path traversal in yaojingang GEOFlow's Image Library Cleanup component allows remote authenticated administrators to delete arbitrary server files by supplying crafted directory-traversal sequences in the `file_path` argument to the PHP `unlink()` function within `ImageLibraryController.php`. All versions up to 2.1.0 are affected (CPE: cpe:2.3:a:yaojingang:geoflow:*:*:*:*:*:*:*:*), with a publicly available proof-of-concept on GitHub issue #60. No CISA KEV listing exists, and the admin-only requirement (PR:H per CVSS 4.0) constrains real-world impact, but the public POC makes patching urgent for any exposed instance.
Arbitrary file write via path traversal in AshAdmin's file upload handler affects versions 0.13.7 through 1.3.0, enabling any authenticated admin user to write attacker-controlled bytes to any filesystem path writable by the BEAM process. The root cause is that browser-supplied filenames are concatenated into upload paths via Elixir's Path.join/1 without stripping directory components, so a crafted filename such as ../../../../var/www/app/priv/static/evil.ex escapes the randomized temp directory. No public exploit has been identified at time of analysis, but the primitive directly enables remote code execution by overwriting application modules, static assets, cron jobs, or SSH authorized_keys files.
Path traversal in SeaCMS up to version 13.6 enables authenticated remote attackers to delete arbitrary files by injecting directory traversal sequences into the `itype` or `vid` parameters of the Comment Cache deletion endpoint `/member.php?action=del_pl`. A public proof-of-concept exploit is documented in a GitHub security advisory, lowering the barrier to exploitation. While not confirmed in CISA KEV, the combination of network reachability, low privilege requirement, and public POC elevates practical risk for exposed SeaCMS deployments beyond what the medium CVSS score alone suggests.
Arbitrary file deletion in SeaCMS up to version 13.6 is achievable by authenticated remote users through the Avatar Upload component's password-change handler, where the `oldpic` parameter is passed unsanitized to PHP's `unlink()` function. A publicly available proof-of-concept exploit hosted on GitHub demonstrates the technique against the `/member.php?action=chgpwdsubmit` endpoint, lowering the barrier for exploitation to any account holder. While the CVSS 4.0 score of 2.1 reflects limited impact - file deletion only, no data exfiltration - deletion of configuration, credential, or application files could cascade into more severe outcomes than the base score implies; no public exploit identified at time of analysis has been confirmed as actively exploited (CISA KEV).
Path traversal in MetaGPT 0.8.1's SPO extension exposes arbitrary server-side files to unauthenticated remote attackers via a crafted FILE_NAME parameter. The flaw in metagpt/ext/spo/utils/load.py allows set_file_name() and load_meta_data() to open attacker-controlled paths - including traversal sequences - without confirming the resolved path remains within the intended settings directory. A public proof-of-concept writeup exists on GitHub; no active exploitation is confirmed in CISA KEV at time of analysis.
Path traversal in Apache Wicket's package resource URL handling exposes files outside the intended package directory to unauthenticated remote attackers, including files under WEB-INF that servlet containers ordinarily protect from direct access. Affected are all releases from 8.0.0 through 8.18.0, 9.0.0 through 9.23.0, and 10.0.0 through 10.10.0. Under default configuration the readable file set is bounded by the SecurePackageResourceGuard's extension allowlist (excluding .xml, .properties, .class), but all configurations unconditionally expose a path-existence oracle usable for reconnaissance, and applications using looser guard configurations can disclose web.xml and other sensitive configuration files. No public exploit identified at time of analysis.
Path traversal in AJCloud's AJY IPC camera firmware (jdbhttpd web service, port 80) allows unauthenticated remote attackers to read arbitrary files with root privileges on devices running firmware prior to 01.10715.11.37. Sensitive data directly accessible includes cleartext RTSP credentials, Wi-Fi SSID and pre-shared key, device serial numbers, and cloud binding parameters, enabling material follow-on attacks beyond the device itself. No public exploit code has been identified at time of analysis, but the attack primitive requires no authentication and no special conditions beyond network reachability.
Zip Slip-style path traversal in Admidio's photo ZIP download feature allows authenticated users who hold album-creation rights to embed directory traversal sequences in album names, which are then reflected verbatim as archive entry paths. When a recipient extracts the resulting ZIP, files may be written outside the intended target directory, providing a limited but real filesystem write primitive on the extracting machine. No public exploit code has been identified at time of analysis; the CVSS 4.0 base score of 2.1 reflects the multiple preconditions - authentication, user interaction, and high attack complexity - that constrain real-world exploitability.
Path traversal in SiYuan 3.8.0 allows an authenticated attacker to read arbitrary files within the workspace directory via the POST /api/template/render endpoint, including conf/conf.json, which contains the API token and cookie signing key. The RenderTemplate function enforces only a workspace-boundary check (util.IsAbsPathInWorkspace) but omits the sensitive-path exclusion (refuseToAccess() blocklist) applied by the file API, creating an inconsistency in access controls across API surfaces. The issue is fixed in v3.8.1; no public exploit identified at time of analysis.
Path traversal in Pake before 3.13.1 allows a malicious or compromised web page loaded inside any Pake-generated desktop app to write attacker-fetched content to arbitrary user-writable filesystem locations, including persistence directories. The `download_file` Tauri command accepted a JavaScript-supplied filename and joined it directly to the Downloads directory without stripping path separators or sanitizing sequences such as `../`, enabling writes to locations such as `~/Library/LaunchAgents/` on macOS, `~/.config/autostart/` on Linux, or the Windows Startup folder. Because the HTTP fetch is performed by the Rust backend rather than the sandboxed browser renderer, browser-level download restrictions do not apply. No public exploit is identified at time of analysis, though the attack primitive is straightforward given JFrog's public disclosure.
Arbitrary file write via path traversal in the WPvivid - Backup, Migration & Staging WordPress plugin (versions before 0.9.133) allows high-privilege WordPress administrators to extract backup archives with traversal sequences that write files outside the designated restore directory. A publicly available proof-of-concept exists per WPScan, though EPSS sits at 0.17% (7th percentile) and CISA KEV lists no active exploitation at time of analysis. Successful exploitation can lead to remote code execution by placing malicious PHP files in web-accessible directories.
Directory traversal in Cloud Commander (coderaiser/cloudcmd) before 19.20.2 lets remote unauthenticated attackers read, write, move, or copy files outside the configured root directory by supplying path-traversal sequences to REST file-operation and markdown endpoints. The root cause is missing path-normalization enforcement before filesystem operations, giving full arbitrary file read/write on the host filesystem. No public exploit identified at time of analysis, but a vendor-released patch (v19.20.2) and a fixing commit with a working url-encoded traversal test case are publicly available, lowering the barrier to reproduction.
Directory traversal in the cohttp OCaml HTTP library before version 6.3.0 allows unauthenticated remote attackers to read arbitrary files outside the configured document root by supplying percent-encoded path traversal sequences such as `..%2f..%2f` in HTTP request URIs. The root cause (CWE-180) is that `Cohttp.Path.resolve_local_file` validated and stripped `.` and `..` segments before percent-decoding the URI, meaning encoded traversal bypassed sanitization entirely. No public exploit code or CISA KEV listing has been identified at time of analysis, but the network-accessible, zero-authentication attack surface makes this a straightforward read primitive for any server using cohttp's static file resolution.
Path traversal in IBM Langflow OSS 1.0.0 through 1.11.1 exposes arbitrary server-side files to unauthenticated remote attackers over the network. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms low-complexity exploitation requiring no credentials or user interaction, with high confidentiality impact limited to file reads - no write or availability impact. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis, but the unauthenticated network vector and low attack complexity make internet-facing instances a realistic opportunistic target once details circulate.
Credential store overwrite in NousResearch Hermes Agent versions 0.16.0 through pre-0.17.0 is achievable by any attacker who can inject content into messages ingested by the agent, exploiting a gap in the sensitive-path guard (CWE-552) that failed to properly exclude auth.json from the file-write tool's reachable paths. By crafting malicious message payloads, an attacker bypasses the path restriction and overwrites the credential store without triggering any protection, resulting in credential tampering and potential unauthorized access to all identities stored therein. No public exploit has been identified at time of analysis, and a vendor-released patch (v0.17.0) is available.
Unauthenticated directory traversal in Yamcs versions up to and including 5.8.6 (per advisory scope, < 5.11.13 per package metadata) allows any remote attacker to read arbitrary files from the underlying host operating system by sending a crafted HTTP request. The flaw resides in StaticFileHandler.java, which resolves user-supplied URL paths against a static file root without verifying the resolved path stays within that root - a double-slash prefix (e.g., //etc/passwd) is sufficient to escape the boundary. No public exploit identified at time of analysis, though the steps-to-reproduce are fully published in the GitHub Security Advisory and the vulnerability was demonstrated in a public CTF challenge at DEFCON 33.
Archive symlink traversal in aquaproj/aqua prior to v2.60.1 enables an attacker who controls a tool archive to write arbitrary files outside the extraction directory with the privileges of the user running aqua. The vulnerable combination in `pkg/unarchive/archives.go` - creating a symlink without destination validation, then following it with a regular file write - allows a malicious tar.gz to overwrite files such as shell startup scripts or PATH entries, resulting in user-level code execution. A working PoC is confirmed in GHSA-mf5c-hw34-4hpp; no CISA KEV listing is present and EPSS data is unavailable for this CVE.
Arbitrary file write in BuilderIO gpt-crawler through 1.5.1 allows unauthenticated remote attackers to overwrite any file on the server filesystem by supplying absolute paths or path traversal sequences in the unsanitized `outputFileName` parameter of the POST /crawl endpoint. File content is sourced from attacker-controlled URLs, making this a combined path traversal and server-side fetch primitive capable of depositing web shells, poisoning cron jobs, or corrupting application configs. No public exploit code or CISA KEV listing exists at time of analysis; the CVSS 4.0 score of 8.8 reflects high integrity impact with no authentication barrier.
Path traversal in Qwen-Agent through 0.0.34 allows unauthenticated remote attackers to read arbitrary files from the server filesystem by supplying absolute paths to the Gradio document-parsing interface. The flaw exists in the simple_doc_parser and supporting utility code, which pass caller-controlled paths directly to file-open operations without restricting access to an intended directory. The CVSS 4.0 score of 8.7 (AV:N/AC:L/PR:N) reflects a zero-prerequisite, network-accessible attack surface; no active exploitation is confirmed in CISA KEV and no public POC has been identified at time of analysis.
Path traversal in Duplicacy's restore function through version 3.2.5 allows arbitrary file writes outside the designated restore directory when a user restores from a compromised or attacker-controlled snapshot repository. Duplicacy fails to sanitize file paths deserialized from snapshot entries, so crafted traversal sequences (e.g., '../../') cause files to be written to any location accessible by the restoring OS user. No public exploit code has been identified at time of analysis and this vulnerability is not listed in the CISA KEV catalog, but the integrity and availability impact is rated High in the CVSS 4.0 assessment.
Path traversal in houtini-lm (versions up to 2.13.2) allows an authenticated remote user to supply crafted absolute paths to the code_task_files tool, causing the server to read files outside its intended working directory. Because code_task_files forwards file contents directly to the configured LLM endpoint - which may be a remote provider such as OpenRouter - a successful traversal can silently exfiltrate sensitive files (SSH keys, environment files, cloud credentials) off the machine to a third-party service. No public exploit has been identified and the CVE has not been added to the CISA KEV catalog; an upstream fix is available in commit 35d97bca.
Path traversal in iswalle getnote-mcp up to version 1.5.0 allows attackers with low-privilege MCP call access to read arbitrary files from the host filesystem via the upload_image tool's unsanitized image_path parameter. The vulnerable fs.readFileSync call in src/index.ts accepts absolute paths and directory traversal sequences, and critically, the read file is automatically uploaded to a public CDN - making this an arbitrary file read with built-in exfiltration, exposing SSH keys, /etc/passwd, and similar sensitive data. A public exploit exists (GitHub issue #10) and vendor-released patch version 1.5.1 is confirmed available; no CISA KEV listing has been identified.
Path traversal and trust inheritance flaws in gitoxide's Rust crates gix (≤ 0.72.0) and gix-validate (≤ 0.10.0) allow an attacker who supplies a malicious repository to read arbitrary git configuration files - including embedded credentials - from a victim system. The attack chains three bugs: a first-occurrence-only `find(b"..")` check in submodule name validation that is bypassed by names like `a..b/../../../.git/`, the fact that this validation function is never invoked in production code, and a trust inheritance flaw in `Submodule::open()` that propagates the parent repository's `Trust::Full` to the traversed path while skipping ownership verification entirely. No public exploit has been identified at time of analysis, though a compiled PoC was referenced (truncated) in the GHSA advisory.
Path traversal in gitoxide before 0.52.1 and gix before 0.83.0 allows an attacker who supplies a malicious git repository to redirect submodule git directory resolution outside .git/modules, exposing arbitrary on-disk repository structure to inspection. The flaw stems from submodule names read from .gitmodules being joined directly as filesystem path components with no normalization or confinement check, so a name such as '../../../escaped-target.git' escapes the expected directory boundary. A proof-of-concept is publicly available via GHSA-fr8x-3vfx-f45h; no confirmed active exploitation at time of analysis.
Path traversal in SiYuan's asset.upload MCP tool before v3.8.1 allows an attacker to exfiltrate arbitrary host files - including SSH keys and credentials - by supplying absolute paths that bypass workspace boundary validation. The attack is delivered via prompt injection against an AI Agent connected to SiYuan's MCP server, meaning exploitation depends on an AI agent processing attacker-controlled content. No public exploit or CISA KEV listing has been identified at time of analysis, but the high confidentiality impact (CVSS 4.0: 6.9) reflects the potential to read any file the SiYuan process can access.
Path traversal in flutter_file_picker's Android implementation (all versions through 10.3.10) allows a malicious Android app on the same device to write arbitrary files into the victim app's internal storage directories. The openFileStream() method in FileUtils.kt constructs file paths using the DISPLAY_NAME value returned by ContentResolver.query() without sanitization, making it trivially exploitable by a crafted ContentProvider that returns filenames containing ../ sequences. No public exploit has been identified at time of analysis; SSVC classifies exploitation as none and the attack is not automatable, keeping real-world risk constrained despite the clear code-level flaw.
Arbitrary file write leading to root remote code execution affects Wazuh worker nodes in clustered deployments running versions 4.4.0 through 4.14.6. A peer that possesses the shared cluster key can abuse the file-synchronization routine to drop, overwrite, or delete files at attacker-chosen paths under /var/ossec - including scripts executed as root - because the worker's non-merged sync branch never verifies that a synced file matches the directory declared by its cluster_item_key. This is an incomplete fix for CVE-2026-30893, and no public exploit has been identified at time of analysis; it is fixed in 4.14.7.
Path traversal in Wazuh's ip-customblock active response script allows low-privileged remote attackers to create or delete arbitrary files as root by injecting directory traversal sequences into the srcip field of alert-triggering log events. Versions prior to 4.14.7 are affected when ip-customblock is configured as an active response - the block action creates an empty file at an attacker-controlled path, while the unblock action deletes it, both executing as root and enabling destruction of credentials, configuration, or other critical files. No public exploit has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog, though the missing validation is trivially observable by comparing ip-customblock.c against its sibling scripts.
Path traversal in MAA-AI MaaMCP (versions up to 1.1.1.dev6+g2e4a41287) allows low-privileged remote users to read or write files outside the intended pipeline directory by supplying crafted path inputs to the save_pipeline and load_pipeline functions in pipeline_tools.py. Publicly available exploit code exists (referenced in GitHub issue #31), though no active exploitation has been confirmed by CISA KEV. The CVSS 4.0 score of 5.1 (Medium) reflects the authentication requirement and limited per-impact severity, but the public POC elevates practical risk above the base score alone.
Path traversal in arben-adm mcp-sequential-thinking versions up to and including 0.5.0 allows remote low-privileged attackers to read or write arbitrary files on the server by supplying unsanitized path sequences to the `import_session` and `export_session` functions in `server.py`. A publicly disclosed proof-of-concept exists (GitHub issue #17), and the fix is available in v0.6.0 via commit 2fad3ee8. The CVE is not listed in CISA KEV, indicating no confirmed mass exploitation, but the public PoC meaningfully elevates practical risk above the moderate CVSS score alone.
Path traversal in RooCodeInc Roo-Code through version 3.51.1 allows remote unauthenticated attackers to read and write files outside the intended working directory by manipulating input processed by the path.resolve function in ApplyPatchTool.ts. The vendor has confirmed they archived the repository and discontinued all support, meaning no patch will ever be released. Publicly available exploit code exists via a GitHub Gist, and no vendor-released patch identified at time of analysis - organizations still running this tool are permanently exposed.
Path traversal via unsanitized MIME attachment filenames in Dolibarr's EmailCollector module allows any email sender to write attacker-controlled files outside the intended attachment directory, affecting versions 9.0.0 through 23.0.4. Because the EmailCollector is designed to ingest mail from unauthenticated external senders - such as a support or ticket inbox - no Dolibarr account is required to exploit this flaw. On hardened deployments with a read-only htdocs tree, the attacker can corrupt or forge documents belonging to other objects; on installations where htdocs is writable, the same write primitive reaches web-executable PHP paths, enabling remote code execution. No public exploit identified at time of analysis.
Zip extraction in AWS diagram-as-code (awsdac) versions 0.10 through 0.23 is vulnerable to relative path traversal (CWE-23), enabling a third party to write arbitrary files outside the intended extraction directory by embedding crafted path sequences in zip entry names within a malicious diagram bundle. Exploitation requires user interaction - a victim must actively process the attacker-supplied bundle - making this a social-engineering-dependent local attack. AWS has released a patched version 0.24; no active exploitation or public exploit code has been identified at time of analysis.
Path traversal in Spring AI's ResourceCacheService allows an authenticated low-privileged network attacker to write files outside the intended cache directory. The getCacheName() method appends URI fragments verbatim - including '../' sequences and path separators - to a base directory path before passing the result to new File(resourceParentFolder, newFileName) and writing downloaded bytes there. Affected versions span Spring AI 1.0.9 and earlier, 1.1.0 through 1.1.8, and 2.0.0; no public exploit or CISA KEV listing has been identified at time of analysis.
Quick Facts
- Typical Severity
- HIGH
- Category
- web
- Total CVEs
- 8417