Skip to main content
CVE-2026-133435VulnerabilityPublished

Keycloak · CWE-178

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133435· Low 3.7

Not known to be exploited · CVSS 3.7 Low.

Data as of 20 Nov 2026, 01:38 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.13.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Build of Keycloakkeycloak-model-jpaAffected–Fixed in–
Red Hat Build of Keycloakrhbk/keycloak-rhel9Affected–Fixed in–
Red Hat Single Sign-On 7keycloak-model-jpaAffected–Fixed in–
Red Hat Single Sign-On 7rh-sso7-keycloakAffected–Fixed in–

AI-suggested

Configure upstream reverse proxies, load balancers, or API gateways to enforce case-insensitive path matching, such as using case-insensitive regular expressions or URI normalization, for rules restricting realm access. Alternatively, enforce network-level restrictions like IP allowlisting or dedicated internal interfaces instead of relying solely on URL path filtering. After configuration changes, reload the proxy service (e.g., `systemctl reload <proxy_service>`) to apply the new settings. Ensure that the proxy path normalization correctly handles all character casing variants.

Description

A vulnerability in Keycloak occurs when it is configured with a database using case-insensitive collation. This causes Keycloak to resolve realm URLs without regard to letter casing, allowing a remote attacker to bypass upstream reverse proxy access controls that rely on case-sensitive path matching. This can expose restricted authentication endpoints intended for internal access. However, Keycloak's internal authentication and access control mechanisms remain effective, preventing unauthorized access without valid credentials.

References

Community reviews

Loading reviews…