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

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CWE-73 (文件名或路径的外部可控制) — Vulnerability Class 431

431 vulnerabilities classified as CWE-73 (文件名或路径的外部可控制). AI Chinese analysis included.

CWE-73 represents a critical input validation weakness where applications allow external actors to dictate file system paths, potentially leading to unauthorized access or modification of sensitive data. Attackers typically exploit this vulnerability through path traversal techniques, injecting sequences like “../” to escape intended directories and reach critical system files or application configurations. This manipulation occurs when software fails to sanitize user-supplied input before using it in filesystem operations, allowing the attacker to bypass intended access controls. To mitigate this risk, developers must implement rigorous input validation, ensuring that all file paths are strictly checked against a whitelist of allowed directories. Additionally, using canonicalization functions to resolve paths before comparison and employing chroot jails can effectively isolate file access, thereby preventing attackers from navigating outside the designated application sandbox.

MITRE CWE Description
The product allows user input to control or influence paths or file names that are used in filesystem operations. This could allow an attacker to access or modify system files or other files that are critical to the application. Path manipulation errors occur when the following two conditions are met: 1. An attacker can specify a path used in an operation on the filesystem. 2. By specifying the resource, the attacker gains a capability that would not otherwise be permitted. For example, the program may give the attacker the ability to overwrite the specified file or run with a configuration controlled by the attacker.
Common Consequences (3)
Integrity, Confidentiality Read Files or Directories, Modify Files or Directories
The application can operate on unexpected files. Confidentiality is violated when the targeted filename is not directly readable by the attacker.
Integrity, Confidentiality, Availability Modify Files or Directories, Execute Unauthorized Code or Commands
The application can operate on unexpected files. This may violate integrity if the filename is written to, or if the filename is for a program or other form of executable code.
Availability DoS: Crash, Exit, or Restart, DoS: Resource Consumption (Other)
The application can operate on unexpected files. Availability can be violated if the attacker specifies an unexpected file that the application modifies. Availability can also be affected if the attacker specifies a filename for a large file, or points to a special device or a file that does not hav…
Mitigations (5)
Architecture and Design When the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap provide this capability.
Architecture and Design, Operation Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict all access to files within a particular directory. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the oper…
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 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…
Effectiveness: High
Implementation Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59).
Examples (2)
The following code uses input from an HTTP request to create a file name. The programmer has not considered the possibility that an attacker could provide a file name such as "../../tomcat/conf/server.xml", which causes the application to delete one of its own configuration files (CWE-22).
String rName = request.getParameter("reportName"); File rFile = new File("/usr/local/apfr/reports/" + rName); ... rFile.delete();
Bad · Java
The following code uses input from a configuration file to determine which file to open and echo back to the user. If the program runs with privileges and malicious users can change the configuration file, they can use the program to read any file on the system that ends with the extension .txt.
fis = new FileInputStream(cfg.getProperty("sub")+".txt"); amt = fis.read(arr); out.println(arr);
Bad · Java
CVE ID Title CVSS Severity Published
CVE-2026-78208 exceljs through 4.4.0 Path Traversal via Unvalidated addImage filename — exceljs 7.5 High 2026-08-24
CVE-2026-62385 NLTK 3.9.4 Path Traversal via FrameNet and NKJP Readers — nltk 5.9 Medium 2026-08-22
CVE-2026-49360 Recce server has unauthenticated SQL execution that allows local file read/write through DuckDB — recce 7.8 High 2026-08-21
CVE-2026-54134 OctoPrint: File exfiltration possible via query parameters on upload endpoints — OctoPrint 7.0 High 2026-08-21
CVE-2026-63343 Arbitrary File Read/Write: metadata.yaml symlink in image allows host filesystem access as root — incus 9.9 Critical 2026-08-21
CVE-2026-48753 Incus has an arbitrary file write via path traversal in S3 multipart upload — incus 9.9 Critical 2026-08-21
CVE-2026-48752 Incus has arbitrary file read+write on host via templates/ symlink in malicious image — incus 9.9 Critical 2026-08-21
CVE-2026-48750 Incus has an arbitrary file write on host via `exec-output` symlink in crafted image — incus 9.9 Critical 2026-08-21
CVE-2026-48749 Incus has an arbitrary file read+write on host via rootfs/ symlink in malicious image — incus 9.9 Critical 2026-08-21
CVE-2026-76158 Datiphy Data Management Center - External Control of File Name or Path — Data Management Center 9.3 Critical 2026-08-21
CVE-2026-77176 Kata-containers: insufficient validation of createcontainer mount and storage rules in genpolicy — Red Hat OpenShift Container Platform 4 8.1 High 2026-08-20
CVE-2026-16926 Vulnerabilities in IBM AIX and PowerVM VIOS — AIX 9.1 Critical 2026-08-20
CVE-2025-36398 DS8900F and DS8A00 Information Disclosure — DS8A00 (R10.0 - R10.1) 5.4 Medium 2026-08-19
CVE-2026-49441 Wazuh : peer-controlled metadata key in process_files_from_worker non-merged branch allows arbitrary file write under WAZUH_PATH on Wazuh manager — wazuh 9.1 Critical 2026-08-19
CVE-2026-20358 Cisco Crosswork Security Hardening Release: August 2026 — Cisco Crosswork Planning 10.0 Critical 2026-08-19
CVE-2026-48162 Wazuh: cluster peer can read arbitrary master files and forge offline REST API administrator tokens via DAPI tmp_file path injection in Wazuh manager — wazuh 9.1 Critical 2026-08-19
CVE-2026-76217 GitPython before 3.1.58 Arbitrary File Read via pathspec-from-file — GitPython 6.5 Medium 2026-08-19
CVE-2026-76210 phpMyFAQ before v4.1.6 Local File Disclosure via PDF Export — phpMyFAQ 6.5 Medium 2026-08-19
CVE-2026-75913 CodeWhale before 0.8.64 Argument Injection via git_show — CodeWhale 9.3 Critical 2026-08-18
CVE-2026-18751 Citrix Workspace App for Mac Security Bulletin for CVE-2026-18751 — WorkSpace App 5.2 Medium 2026-08-18
CVE-2026-75830 grav-plugin-api before 1.0.15 Path Traversal via batchCopy — grav 7.1 High 2026-08-18
CVE-2026-74884 openssl_encrypt before 1.4.0 Path Traversal via plugin_id — openssl_encrypt 7.5 High 2026-08-17
CVE-2026-34492 Airwall - Arbitrary file read — Airwall 7.0 High 2026-08-14
CVE-2026-17184 IBM Db2 Mirror for i is affected by multiple vulnerabilities — Db2 Mirror for i 9.8 Critical 2026-08-14
CVE-2026-72841 luci-app-openvpn Path Traversal RCE via instance_name2 — luci 9.9 Critical 2026-08-13
CVE-2026-72842 OpenWrt luci-app-lxc ACL Inconsistency Authentication Bypass — luci 9.9 Critical 2026-08-13
CVE-2026-17482 IBM Documentation Offline is vulnerable to information disclosure, session forgery and remote code execution — Documentation Offline 9.8 Critical 2026-08-13
CVE-2026-16987 IBM i is Affected By An Improper Validation Vulnerability in PASE [] — i 8.8 High 2026-08-13
CVE-2026-16898 IBM i is Affected By Multiple Vulnerabilities in Network Authentication Service — i 7.8 High 2026-08-13
CVE-2026-45725 compliance-trestle Remote Fetching Mechanism has an Arbitrary File Write via Cache Path Traversal — compliance-trestle 7.1 High 2026-08-13

Vulnerabilities classified as CWE-73 (文件名或路径的外部可控制) represent 431 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.