CWE · MITRE source
CWE-24Path Traversal: '../filedir'
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory.
This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory. The "../" manipulation is the canonical manipulation for operating systems that use "/" as directory separators, such as UNIX- and Linux-based systems. In some cases, it is useful for bypassing protection schemes in environments for which "/" is supported but not the primary separator, such as Windows, which uses "\" but can also accept "/".
Last updated: 15 October 2026 20:36 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-38129 UPD | 8.6 | 9.8 | 0.2138 | 2022-08-10 |
CVE-2025-27920 KEV UPD | 8.0 | 7.2 | 0.0186 | 2025-05-05 |
CVE-2026-39813 | 7.4 | 9.8 | 0.0072 | 2026-04-14 |
CVE-2025-60344 UPD | 7.2 | 8.6 | 0.1089 | 2025-10-21 |
CVE-2021-33036 UPD | 7.1 | 8.8 | 0.0397 | 2022-06-15 |
CVE-2025-54769 UPD | 7.1 | 8.8 | 0.0333 | 2025-07-29 |
CVE-2023-6699 UPD | 7.0 | 9.1 | 0.0086 | 2024-01-11 |
CVE-2025-61318 UPD | 7.0 | 9.1 | 0.0073 | 2025-12-08 |
CVE-2024-23657 UPD | 6.8 | 8.8 | 0.0121 | 2024-08-05 |
CVE-2026-108980 | 6.8 | 8.8 | 0.0106 | 2026-10-12 |
CVE-2025-53513 UPD | 6.7 | 8.8 | 0.0078 | 2025-07-08 |
CVE-2023-1800 UPD | 6.3 | 7.3 | 0.0355 | 2023-04-02 |
CVE-2023-53691 UPD | 6.3 | 8.3 | 0.0129 | 2025-10-22 |
CVE-2025-63298 | 6.3 | 8.2 | 0.0052 | 2025-10-30 |
CVE-2026-66140 UPD | 6.3 | 8.4 | 0.0039 | 2026-07-24 |
CVE-2023-52076 UPD | 6.2 | 8.5 | 0.0109 | 2024-01-25 |
CVE-2025-59049 UPD | 6.2 | 7.5 | 0.0176 | 2025-09-10 |
CVE-2026-97730 | 6.2 | 8.5 | 0.0103 | 2026-09-25 |
CVE-2020-7882 UPD | 6.1 | 7.5 | 0.0130 | 2021-11-22 |
CVE-2026-40318 | 6.1 | 8.5 | 0.0044 | 2026-04-16 |
CVE-2022-36065 UPD | 6.0 | 7.5 | 0.0143 | 2022-09-06 |
CVE-2024-22079 UPD | 6.0 | 7.5 | 0.0102 | 2024-03-20 |
CVE-2025-51661 | 5.9 | 7.5 | 0.0053 | 2025-11-19 |
CVE-2025-67364 UPD | 5.9 | 7.5 | 0.0063 | 2026-01-07 |
CVE-2026-28427 UPD | 5.9 | 7.5 | 0.0051 | 2026-03-04 |