CVE-2026-133435
Description
A flaw was found in Keycloak. When configured with a database that uses case-insensitive collation, Keycloak resolves realm URLs regardless of letter casing. A remote attacker can exploit this behavior by sending requests with alternate letter casing to bypass upstream reverse proxy access controls that rely on case-sensitive path matching. This issue can expose restricted authentication endpoints intended only for internal access, though Keycloak's internal authentication mechanisms remain intact.
Statement
This vulnerability is rated as having a Low severity impact because it only allows bypassing path-based filtering rules on an external reverse proxy and does not bypass Keycloak's internal authentication or access control mechanisms. In typical deployments where an upstream gateway relies on case-sensitive URL rules to block public access to internal realm endpoints, a remote requester can access the login interface via alternate character casing if Keycloak is backed by a database configured with case-insensitive collation. Even when exposed, Keycloak still enforces standard user authentication and permission checks, preventing unauthorized data access or session establishment without valid credentials.
Mitigation
Configure upstream reverse proxies, load balancers, or API gateways to enforce case-insensitive path matching (such as case-insensitive regular expressions or URI normalization) for rules restricting realm access. Alternatively, enforce network-level restrictions (such as IP allowlisting or dedicated internal interfaces) instead of URL path filtering alone.
Apply the revised configuration by reloading the proxy service:
`systemctl reload <proxy_service>`
Warning: Reloading or restarting the proxy service may momentarily disrupt active client connections. Ensure that proxy path normalization accurately handles all character casing variants.
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 | 3.7 | N/A | 3.7 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | Low |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
Improperly handled case sensitive data can lead to several possible consequences, including: - case-insensitive passwords reducing the size of the key space, making brute force attacks easier - bypassing filters or access controls using alternate names - multiple interpretation errors using alternate names.
Acknowledgements
Red Hat would like to thank Alexander Schwartz (IBM) for reporting this issue.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.