Project Subscriptions
No advisories yet.
Solution
No solution given by the vendor.
Workaround
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.
Thu, 19 Nov 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Org.keycloak:keycloak-model-jpa: case-variant realm urls bypass proxy restrictions | |
| First Time appeared |
Redhat
Redhat build Keycloak Redhat red Hat Single Sign On |
|
| Weaknesses | CWE-178 | |
| CPEs | cpe:/a:redhat:build_keycloak: cpe:/a:redhat:red_hat_single_sign_on:7 |
|
| Vendors & Products |
Redhat
Redhat build Keycloak Redhat red Hat Single Sign On |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-11-19T22:35:34.078Z
Reserved: 2026-11-19T19:52:40.942Z
Link: CVE-2026-133435
No data.
No data.
No data.
OpenCVE Enrichment
No data.