Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CWE-22 (对路径名的限制不恰当(路径遍历)) — Vulnerability Class 5199

5199 vulnerabilities classified as CWE-22 (对路径名的限制不恰当(路径遍历)). AI Chinese analysis included.

CWE-22 represents a critical input validation weakness where software fails to properly sanitize external input before constructing file paths. Attackers typically exploit this vulnerability by injecting directory traversal sequences, such as “../”, into user-supplied parameters. These malicious inputs allow the application to resolve file references outside the intended restricted directory, potentially granting unauthorized access to sensitive system files, configuration data, or source code. To mitigate this risk, developers must implement rigorous input validation techniques, ensuring that all path components are strictly checked against allowed characters and structures. Additionally, employing canonicalization to resolve symbolic links and relative paths before validation, combined with strict chroot jails or sandboxing, effectively confines file operations to designated directories, thereby neutralizing the potential for path traversal attacks and preserving system integrity.

MITRE CWE Description
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Many file operations are intended to take place within a restricted directory. By using special elements such as ".." and "/" separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is the "../" sequence, which in most modern operating systems is interpreted as the parent directory of the current location. This is referred to as relative path traversal. Path traversal also covers the use of absolute pathnames such as "/usr/local/bin" to access unexpected files. This is referred to as absolute path traversal.
Common Consequences (4)
Integrity, Confidentiality, Availability Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow …
Confidentiality Read Files or Directories
The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing a…
Availability DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Mitigations (5)
Implementation Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range…
Architecture and Design For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Implementation Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked. Use a built-in path canonicalization function (such as realpath(…
Architecture and Design Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
Operation Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
Effectiveness: Moderate
Examples (2)
The following code could be for a social networking application in which each user's profile information is stored in a separate file. All files are stored in a single directory.
my $dataPath = "/users/cwe/profiles"; my $username = param("user"); my $profilePath = $dataPath . "/" . $username; open(my $fh, "<", $profilePath) || ExitError("profile read error: $profilePath"); print "<ul>\n"; while (<$fh>) { print "<li>$_</li>\n"; } print "</ul>\n";
Bad · Perl
../../../etc/passwd
Attack
In the example below, the path to a dictionary file is read from a system property and used to initialize a File object.
String filename = System.getProperty("com.domain.application.dictionaryFile"); File dictionaryFile = new File(filename);
Bad · Java
CVE ID Title CVSS Severity Published
CVE-2026-45711 Mailpit: Path traversal & arbitrary file write in mailpit dump --http via attacker-controlled message IDs — mailpit 5.9 Medium 2026-07-20
CVE-2026-54910 FileBrowser Quantum's path traversal issue in subtitle handler allows any authenticated user to read arbitrary files — filebrowser 7.7 High 2026-07-20
CVE-2026-12701 Pulpcore: pulpcore: relative_path_validator bypass via directory traversal in filesystemexport — Red Hat Ansible Automation Platform 2.5 for RHEL 8 9.0 Critical 2026-07-20
CVE-2026-63739 SurrealDB before 3.1.5 Arbitrary File Read via DEFINE ANALYZER — surrealdb 7.7 High 2026-07-20
CVE-2026-16219 Croogo CMS Admin File Manager FileManager.php isEditable path traversal — CMS 6.3 Medium 2026-07-19
CVE-2025-71394 SurrealDB before 2.2.2 Local File Read via DEFINE ANALYZER — surrealdb 2.3 Low 2026-07-18
CVE-2026-15631 @fastify/http-proxy vulnerable to prefix escape via WebSocket path traversal — @fastify/http-proxy 8.7 High 2026-07-18
CVE-2026-16088 halo-dev halo Files Backup Endpoint MigrationEndpoint.java download path traversal — halo 4.7 Medium 2026-07-18
CVE-2026-47871 VMware Avi Load Balancer Directory Traversal Vulnerability — Avi Load Balancer 8.8 High 2026-07-18
CVE-2026-48049 @hapi/inert: Static-file confinement bypass via sibling-prefix path — inert 5.3 Medium 2026-07-17
CVE-2026-50163 oras-go: Hardlink entry with relative Linkname escapes extract dir via process CWD resolution in `oras-go` tar extraction — oras-go 7.1 High 2026-07-17
CVE-2026-7667 Path Traversal Vulnerability in API Request Component Content-Disposition Header Processing — Langflow OSS 8.8 High 2026-07-17
CVE-2026-7872 Path Traversal Vulnerability in File Component Leading to Arbitrary File Read and Authentication Bypass — Langflow OSS 7.5 High 2026-07-17
CVE-2026-8859 Path Traversal in APIRequest Component via Content-Disposition Header — Langflow OSS 9.9 Critical 2026-07-17
CVE-2026-45309 AsyncSSH `AuthorizedKeysFile %u` path traversal allows attacker-selected authorized keys to authenticate a traversal username — asyncssh - - 2026-07-17
CVE-2026-15343 Path traversal vulnerability in GitHub Enterprise Server allowed writing files to arbitrary repository paths, including GitHub Actions workflow files, via unchecked Dependabot dependency-file paths — Enterprise Server - - 2026-07-17
CVE-2026-15457 Kirki <= 6.0.13 - Authenticated (Editor+) Path Traversal to Arbitrary Directory Deletion via 'family' Parameter — Kirki – Freeform Page Builder, Website Builder & Customizer 4.9 Medium 2026-07-17
CVE-2026-15160 Ninja Forms - Excel Export <= 3.3.6 - Missing Authorization to Authenticated (Subscriber+) XLS Write via Path Traversal — Ninja Forms - Excel Export 4.3 Medium 2026-07-17
CVE-2026-62229 OpenClaw < 2026.5.18 Authorization Bypass via Glob Matching — OpenClaw 8.8 High 2026-07-17
CVE-2026-39359 Wazuh: Unauthenticated Path Traversal in authd via Agent Group Name — wazuh 7.5 High 2026-07-16
CVE-2026-44177 Kirby: Pre-authentication path traversal and PHP file inclusion during user lookup — kirby - - 2026-07-16
CVE-2026-44023 Docling Core has unsafe remote filename resolution — docling-core 8.6 High 2026-07-16
CVE-2026-55629 Whistle: Path traversal — whistle - - 2026-07-16
CVE-2026-53535 Activepieces: Arbitrary file write in git-sync via path traversal and symlinks — activepieces - - 2026-07-16
CVE-2026-46338 PyMdown Extensions: Regression in pymdownx.snippets reintroduces sibling-prefix path traversal bypass despite restrict_base_path — pymdown-extensions 4.3 Medium 2026-07-16
CVE-2026-46336 Manyfold: Authenticated Path Traversal via File Rename — manyfold 7.1 High 2026-07-16
CVE-2026-13103 Lenovo app store 路径遍历漏洞 — App Store 7.3 High 2026-07-16
CVE-2026-45576 zrok copy writes attacker-controlled WebDAV paths outside the destination root — zrok - - 2026-07-16
CVE-2026-45568 zrok Python ProxyShare can be used as an SSRF proxy through absolute URL paths — zrok - - 2026-07-16
CVE-2026-53598 Prompty: Arbitrary File Read via ${file:path} Reference Expansion — prompty 7.5 High 2026-07-16

Vulnerabilities classified as CWE-22 (对路径名的限制不恰当(路径遍历)) represent 5199 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.