Security Resilience

CWE · MITRE source

CWE-647Use of Non-Canonical URL Paths for Authorization Decisions

Abstraction: Variant · CVEs in our corpus: 15

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.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • PR.AA-05
  • AC-3 Access Enforcement
Detect
Catch it (CSF Detect / Respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V2.2.1
  • V10.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 9.28.60.92272023-04-03
CVE-2026-597316.38.20.00472026-07-08
CVE-2026-626856.28.10.00552026-07-15
CVE-2025-64500 6.07.30.01412025-11-12
CVE-2025-66202 5.16.50.00312025-12-09
CVE-2026-5222 5.16.50.00502026-05-25
CVE-2025-9909 4.96.70.00172026-02-27
CVE-2026-73551 4.55.30.00532026-09-21
CVE-2026-83844.45.30.00332026-07-14
CVE-2025-47241 3.44.00.00452025-05-03
CVE-2026-15970 3.44.20.00212026-08-07
CVE-2026-711783.13.70.00162026-09-23
CVE-2025-43916 2.83.40.00222025-04-21