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: 14 October 2026 20:41 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-2026-85978 | 7.6 | 9.8 | 0.0144 | 2026-09-09 |
CVE-2026-102217 | 6.8 | 8.8 | 0.0111 | 2026-10-13 |
CVE-2026-108463 | 6.7 | 8.8 | 0.0088 | 2026-10-13 |
CVE-2026-88136 | 6.7 | 8.8 | 0.0095 | 2026-10-13 |
CVE-2025-24470 UPD | 6.5 | 8.6 | 0.0133 | 2025-02-11 |
CVE-2023-36396 UPD | 6.2 | 7.8 | 0.0167 | 2023-11-14 |
CVE-2026-23674 | 6.1 | 7.5 | 0.0124 | 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.0084 | 2025-03-20 |
CVE-2026-5816 | 5.8 | 8.0 | 0.0059 | 2026-04-22 |
CVE-2026-70184 | 5.8 | 7.8 | 0.0038 | 2026-10-13 |
CVE-2025-43298 UPD | 5.7 | 7.8 | 0.0025 | 2025-09-15 |
CVE-2024-30036 UPD | 5.5 | 6.5 | 0.0229 | 2024-05-14 |
CVE-2026-102231 | 5.4 | 7.7 | 0.0038 | 2026-10-13 |
CVE-2026-72835 UPD | 5.3 | 6.8 | 0.0050 | 2026-08-14 |
CVE-2023-46169 UPD | 5.1 | 6.5 | 0.0051 | 2024-03-07 |
CVE-2026-49401 | 5.1 | 7.3 | 0.0020 | 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.0074 | 2025-03-20 |
CVE-2026-34510 | 4.5 | 5.3 | 0.0046 | 2026-04-01 |
CVE-2026-66064 | 4.5 | 5.3 | 0.0044 | 2026-07-28 |
CVE-2026-93709 | 4.4 | 5.3 | 0.0033 | 2026-09-22 |
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 |