CWE · MITRE source
CWE-426Untrusted Search Path
The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control.
This might allow attackers to execute their own programs, access unauthorized data files, or modify configuration in unexpected ways. If the product uses a search path to locate critical resources such as programs, then an attacker could modify that search path to point to a malicious program, which the targeted product would then execute. The problem extends to any type of critical resource that the product trusts. Some of the most common variants of untrusted search path are:
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: full · 8 mapping(s) from 3 framework(s): ATT&CK 6 (full) · OWASP-Web 1 (mostly) · CAPEC 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A08:2025 Software or Data Integrity Failures.
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-2012-1854 KEV | 10.0 | 7.8 | 0.2103 | 2012-07-10 |
CVE-2022-22047 KEV | 10.0 | 7.8 | 0.1891 | 2022-07-12 |
CVE-2022-23748 KEV | 10.0 | 7.8 | 0.0909 | 2022-11-17 |
CVE-2015-0096 | 8.0 | 0.0 | 0.7107 | 2015-03-11 |
CVE-2017-2225 | 7.0 | 9.8 | 0.0147 | 2017-07-07 |
CVE-2017-12414 | 7.0 | 9.8 | 0.0157 | 2017-08-03 |
CVE-2018-19486 | 7.0 | 9.8 | 0.0412 | 2018-11-23 |
CVE-2020-15801 | 7.0 | 9.8 | 0.0310 | 2020-07-17 |
CVE-2011-4125 | 7.0 | 9.8 | 0.0223 | 2021-10-27 |
CVE-2022-26184 | 7.0 | 9.8 | 0.0183 | 2022-03-21 |
CVE-2022-24826 | 7.0 | 9.8 | 0.0208 | 2022-04-20 |
CVE-2023-30330 | 7.0 | 9.8 | 0.0588 | 2023-05-12 |
CVE-2024-38462 | 7.0 | 9.8 | 0.0061 | 2024-06-16 |
CVE-2024-53866 | 7.0 | 9.8 | 0.0094 | 2024-12-10 |
CVE-2025-31480 | 7.0 | 9.1 | 0.0043 | 2025-04-04 |
CVE-2024-58250 UPD | 7.0 | 9.3 | 0.0020 | 2025-04-22 |
CVE-2025-23266 UPD | 7.0 | 9.0 | 0.0254 | 2025-07-17 |
CVE-2025-49457 UPD | 7.0 | 9.6 | 0.0054 | 2025-08-12 |
CVE-2025-26155 | 7.0 | 9.8 | 0.0050 | 2025-11-26 |
CVE-2026-45772 UPD | 7.0 | 9.8 | 0.0039 | 2026-05-15 |
CVE-2026-45721 UPD | 7.0 | 9.0 | 0.0044 | 2026-05-26 |
CVE-2026-44477 UPD | 7.0 | 9.9 | 0.0048 | 2026-05-28 |
CVE-2011-2019 | 6.0 | 0.0 | 0.1297 | 2011-12-14 |
CVE-2014-0315 | 6.0 | 0.0 | 0.1474 | 2014-04-08 |
CVE-2016-0016 | 6.0 | 7.8 | 0.3109 | 2016-01-13 |