CWE · MITRE source
CWE-647Use of Non-Canonical URL Paths for Authorization Decisions
The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical. This can allow a non-canonical URL to bypass the authorization.
If an application defines policy namespaces and makes authorization decisions based on the URL, but it does not require or convert to a canonical URL before making the authorization decision, then it opens the application to attack. For example, if the application only wants to allow access to http://www.example.com/mypage, then the attacker might be able to bypass this restriction using equivalent URLs such as: Therefore it is important to specify access control policy that is based on the path information in some canonical form with all alternate encodings rejected (which can be accomplished by a default deny rule).
Last updated: 15 October 2026 14:21 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
—
V2.2.1V10.4.1
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-43939 KEV UPD | 9.2 | 8.6 | 0.9227 | 2023-04-03 |
CVE-2026-59731 | 6.3 | 8.2 | 0.0047 | 2026-07-08 |
CVE-2026-62685 | 6.2 | 8.1 | 0.0055 | 2026-07-15 |
CVE-2025-64500 UPD | 6.0 | 7.3 | 0.0141 | 2025-11-12 |
CVE-2025-66202 UPD | 5.1 | 6.5 | 0.0031 | 2025-12-09 |
CVE-2026-5222 UPD | 5.1 | 6.5 | 0.0050 | 2026-05-25 |
CVE-2025-9909 UPD | 4.9 | 6.7 | 0.0017 | 2026-02-27 |
CVE-2026-73551 UPD | 4.5 | 5.3 | 0.0053 | 2026-09-21 |
CVE-2026-8384 | 4.4 | 5.3 | 0.0033 | 2026-07-14 |
CVE-2025-47241 UPD | 3.4 | 4.0 | 0.0045 | 2025-05-03 |
CVE-2026-15970 UPD | 3.4 | 4.2 | 0.0021 | 2026-08-07 |
CVE-2026-71178 | 3.1 | 3.7 | 0.0016 | 2026-09-23 |
CVE-2025-43916 UPD | 2.8 | 3.4 | 0.0022 | 2025-04-21 |