CWE-551Base

Incorrect Behavior Order: Authorization Before Parsing and Canonicalization

Incomplete in the CWE catalog · 20 CVEs mapped

20
CVEs mapped
7.9
Median CVSS
What it is

If a web server does not fully parse requested URLs before it examines them for authorization, it may be possible for an attacker to bypass authorization protection.

Recent examples
8.1cvss
CVE-2026-16102

CVE-2026-16102 - HIGH Severity Vulnerability

A flaw was found in the Dynamic Client Registration (DCR) component of Keycloak, an identity and access management solution. The default DCR policy fails to properly validate the claim path for User Property mappers, allowing them to write values to sensitive internal claim locations. An attacker with a standard user account and a limited Initial Access Token can exploit this to forge administrative roles in their access token. This allows the attacker to take over other clients, steal confidential secrets, and potentially gain full administrative control over the realm.

HIGHno explanation yet
0%
epss
8.1cvss
CVE-2026-15573

CVE-2026-15573 - HIGH Severity Vulnerability

A flaw was found in Keycloak's Authorization Services. The component responsible for matching request paths to security policies (PathMatcher) does not properly normalize URIs before comparison. By adding extra characters like a trailing slash or matrix parameters to a URL, an attacker can trick the system into applying a less restrictive security policy than intended. This allows an authenticated user to access administrative or restricted areas they should not have permission to see.

HIGHno explanation yet
0%
epss
7.5cvss
CVE-2026-13676

CVE-2026-13676 - HIGH Severity Vulnerability

fast-uri versions 2.3.1 through 3.1.2 and 4.0.0 fail to canonicalize Unicode (IDN) hostnames for HTTP-family URLs. The IDN conversion path calls a helper that does not exist on the global URL constructor, silently leaving the host in its original Unicode form while normalize() and equal() still return values that differ from a WHATWG-compatible URL parser. Applications that use fast-uri to enforce host-based policy (denylists, loopback filtering, redirect validation, outbound proxy routing) before passing the same URL to Node's URL or fetch can be bypassed when the two implementations resolve the same input to different hosts. Patches: upgrade to fast-uri 3.1.3 for the 3.x line or 4.0.1 for the 4.x line. Workarounds: enforce host policy using the same URL parser used for the actual request, or reject non-ASCII hosts before policy checks.

HIGHno explanation yet
0%
epss
The record
Technical detail
CWE ID
CWE-551
Abstraction
Base
Structure
Simple
Status
Incomplete