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: 04 July 2026 08:17 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 · 3 mapping(s) from 2 framework(s): ATT&CK 2 (partial) · CAPEC 1 (partial)
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2023-36396 | 5.5 | 7.8 | 0.0167 | 2023-11-14 |
CVE-2024-30073 | 5.5 | 7.8 | 0.0090 | 2024-09-10 |
CVE-2025-24470 | 5.5 | 8.6 | 0.0123 | 2025-02-11 |
CVE-2024-8765 | 5.5 | 7.3 | 0.0078 | 2025-03-20 |
CVE-2025-43298 | 5.5 | 7.8 | 0.0022 | 2025-09-15 |
CVE-2026-23674 | 5.5 | 7.5 | 0.0119 | 2026-03-10 |
CVE-2026-5816 | 5.5 | 8.0 | 0.0041 | 2026-04-22 |
CVE-2026-49401 | 5.5 | 7.3 | 0.0014 | 2026-06-23 |
CVE-2022-0855 | 3.5 | 6.1 | 0.0097 | 2022-03-04 |
CVE-2023-46169 | 3.5 | 6.5 | 0.0051 | 2024-03-07 |
CVE-2024-30036 | 3.5 | 6.5 | 0.0229 | 2024-05-14 |
CVE-2024-45405 | 3.5 | 6.0 | 0.0026 | 2024-09-06 |
CVE-2025-21189 | 3.5 | 4.3 | 0.0286 | 2025-01-14 |
CVE-2025-21219 | 3.5 | 4.3 | 0.0291 | 2025-01-14 |
CVE-2025-21268 | 3.5 | 4.3 | 0.0192 | 2025-01-14 |
CVE-2025-21269 | 3.5 | 4.3 | 0.0443 | 2025-01-14 |
CVE-2025-21328 | 3.5 | 4.3 | 0.0146 | 2025-01-14 |
CVE-2025-21329 | 3.5 | 4.3 | 0.0146 | 2025-01-14 |
CVE-2025-21332 | 3.5 | 4.3 | 0.0142 | 2025-01-14 |
CVE-2025-21247 | 3.5 | 4.3 | 0.0298 | 2025-03-11 |
CVE-2024-6839 | 3.5 | 5.3 | 0.0065 | 2025-03-20 |
CVE-2025-54107 | 3.5 | 4.3 | 0.0086 | 2025-09-09 |
CVE-2026-34451 | 3.5 | 5.4 | 0.0029 | 2026-03-31 |
CVE-2026-34510 | 3.5 | 5.3 | 0.0032 | 2026-04-01 |
CVE-2025-58290 | 1.5 | 3.3 | 0.0010 | 2025-10-11 |