CWE · MITRE source
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
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.
Last updated: 22 August 2026 20:22 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: mostly · 6 mapping(s) from 2 framework(s): CAPEC 5 (mostly) · CSF 2.0 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A01:2025 Broken Access Control.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls that address this weakness (1)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SI-10 | Information Input Validation | SI | Validates pathnames and filenames to prevent traversal outside intended directories. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2019-11510 KEV UPD | 10.0 | 10.0 | 1.0000 | 2019-05-08 |
CVE-2021-41277 KEV UPD | 10.0 | 10.0 | 0.9718 | 2021-11-17 |
CVE-2025-34028 KEV UPD | 10.0 | 10.0 | 0.9766 | 2025-04-22 |
CVE-2026-34909 KEV UPD | 10.0 | 10.0 | 0.6390 | 2026-05-22 |
CVE-2026-48282 KEV UPD | 10.0 | 10.0 | 0.9924 | 2026-06-30 |
CVE-2004-0847 UPD | 9.9 | 9.8 | 0.7570 | 2004-11-03 |
CVE-2010-2861 KEV UPD | 9.9 | 9.8 | 0.9972 | 2010-08-11 |
CVE-2014-0780 KEV UPD | 9.9 | 9.8 | 0.7455 | 2014-04-25 |
CVE-2016-6600 UPD | 9.9 | 9.8 | 0.9055 | 2017-01-23 |
CVE-2016-7552 UPD | 9.9 | 9.8 | 0.9325 | 2017-04-12 |
CVE-2015-9266 UPD | 9.9 | 9.8 | 0.7400 | 2018-09-05 |
CVE-2019-3396 KEV UPD | 9.9 | 9.8 | 0.9991 | 2019-03-25 |
CVE-2019-12314 UPD | 9.9 | 9.8 | 0.8422 | 2019-05-24 |
CVE-2019-1620 UPD | 9.9 | 9.8 | 0.8378 | 2019-06-27 |
CVE-2019-16278 KEV UPD | 9.9 | 9.8 | 0.9903 | 2019-10-14 |
CVE-2019-17662 UPD | 9.9 | 9.8 | 0.9676 | 2019-10-16 |
CVE-2019-7194 KEV UPD | 9.9 | 9.8 | 0.8312 | 2019-12-05 |
CVE-2019-7195 KEV UPD | 9.9 | 9.8 | 0.8968 | 2019-12-05 |
CVE-2019-19781 KEV UPD | 9.9 | 9.8 | 1.0000 | 2019-12-27 |
CVE-2014-8741 UPD | 9.9 | 9.8 | 0.7720 | 2020-01-27 |
CVE-2020-6754 UPD | 9.9 | 9.8 | 0.9480 | 2020-02-05 |
CVE-2020-11455 UPD | 9.9 | 9.8 | 0.9718 | 2020-04-01 |
CVE-2020-3247 UPD | 9.9 | 9.8 | 0.7507 | 2020-04-15 |
CVE-2020-3248 UPD | 9.9 | 9.8 | 0.7391 | 2020-04-15 |
CVE-2020-5902 KEV UPD | 9.9 | 9.8 | 1.0000 | 2020-07-01 |