CWE · MITRE source
CWE-41Improper Resolution of Path Equivalence
The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object.
Path equivalence is usually employed in order to circumvent access controls expressed using an incomplete set of file name or file path representations. This is different from path traversal, wherein the manipulations are performed to generate a name for a different object.
Last updated: 20 August 2026 13:14 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: partial · 1 mapping(s) from 1 framework(s): CAPEC 1 (partial)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls that address this weakness (0)AI-assisted
| 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-2025-24470 UPD | 6.5 | 8.6 | 0.0130 | 2025-02-11 |
CVE-2023-36396 UPD | 6.2 | 7.8 | 0.0167 | 2023-11-14 |
CVE-2026-23674 | 6.1 | 7.5 | 0.0119 | 2026-03-10 |
CVE-2024-30073 UPD | 6.0 | 7.8 | 0.0090 | 2024-09-10 |
CVE-2024-8765 UPD | 5.9 | 7.3 | 0.0081 | 2025-03-20 |
CVE-2025-43298 UPD | 5.7 | 7.8 | 0.0024 | 2025-09-15 |
CVE-2026-5816 | 5.7 | 8.0 | 0.0041 | 2026-04-22 |
CVE-2024-30036 UPD | 5.5 | 6.5 | 0.0229 | 2024-05-14 |
CVE-2026-72835 | 5.2 | 6.8 | 0.0034 | 2026-08-14 |
CVE-2023-46169 UPD | 5.1 | 6.5 | 0.0051 | 2024-03-07 |
CVE-2026-49401 | 5.1 | 7.3 | 0.0019 | 2026-06-23 |
CVE-2022-0855 UPD | 4.8 | 6.1 | 0.0099 | 2022-03-04 |
CVE-2024-45405 UPD | 4.6 | 6.0 | 0.0026 | 2024-09-06 |
CVE-2024-6839 UPD | 4.6 | 5.3 | 0.0068 | 2025-03-20 |
CVE-2026-34510 | 4.4 | 5.3 | 0.0032 | 2026-04-01 |
CVE-2026-66064 | 4.4 | 5.3 | 0.0031 | 2026-07-28 |
CVE-2025-21269 UPD | 4.3 | 4.3 | 0.0459 | 2025-01-14 |
CVE-2025-21189 UPD | 4.2 | 4.3 | 0.0297 | 2025-01-14 |
CVE-2025-21219 UPD | 4.2 | 4.3 | 0.0302 | 2025-01-14 |
CVE-2025-21247 UPD | 4.2 | 4.3 | 0.0324 | 2025-03-11 |
CVE-2025-21268 UPD | 4.1 | 4.3 | 0.0199 | 2025-01-14 |
CVE-2026-34451 UPD | 4.1 | 5.4 | 0.0035 | 2026-03-31 |
CVE-2025-21328 UPD | 4.0 | 4.3 | 0.0152 | 2025-01-14 |
CVE-2025-21329 UPD | 4.0 | 4.3 | 0.0152 | 2025-01-14 |
CVE-2025-21332 UPD | 4.0 | 4.3 | 0.0147 | 2025-01-14 |