CVE-2026-133537
Description
A flaw was found in Keycloak. When evaluating access permissions, Keycloak Authorization Services improperly matches resource paths containing wildcard file extensions by evaluating only the file extension suffix and ignoring configured path prefixes. An authenticated remote attacker could exploit this vulnerability by requesting a restricted resource that shares a file extension with a more permissive resource, leading to an authorization bypass and unintended access to protected data.
Statement
This vulnerability is rated as Moderate severity rather than Important because successful exploitation requires a specific, non-standard authorization policy configuration where resources define extension suffix wildcards across overlapping path boundaries. In typical Red Hat deployments utilizing Keycloak Authorization Services, resource URIs are mapped explicitly or use prefix wildcards, which are not susceptible to this flaw. When vulnerable suffix patterns are present alongside more restrictive policies, authenticated users may receive unintended access grants, bypassing intended path-level authorization checks.
Mitigation
Avoid using extension wildcard patterns in Keycloak Authorization Services resource definitions.
Review configured resource URIs within the Keycloak administration console under Clients > [Client] > Authorization > Resources. Replace any URI pattern relying on extension suffix wildcards (for example, `/public/*.json`) with explicit path definitions or standard directory wildcard patterns (such as `/public/*`).
Caveat: Modifying resource URI matching patterns may alter authorization policy evaluation and require aligning client requests or application routing with the revised resource definitions.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.8 | N/A | 6.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
The regexp could accept substrings that match the pattern, which produces a partial comparison to the target. In some cases, this can allow dangerous substrings to bypass the intended protection.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.