Skip to main content
VulnerabilityPublished

CVE-2026-133225: Red Hat Build of Keycloak · Improperly Implemented Security Check for Standard

Affects Red Hat Build of KeycloakSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 20 Nov 2026, 01:50 UTC

CVSS 3.1 base score
5.4Medium
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.15.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 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-servicesAffected–Fixed in–
Red Hat Build of Keycloakrhbk/keycloak-rhel9Affected–Fixed in–
Red Hat Single Sign-On 7keycloak-servicesAffected–Fixed in–
Red Hat Single Sign-On 7rh-sso7-keycloakAffected–Fixed in–

AI-suggested

Red Hat currently does not provide a mitigation or fix that meets its criteria for ease of use, applicability, or stability. Users should be aware that typical deployments enforcing online token introspection or client status verification reduce the impact of this vulnerability. Monitor Red Hat's advisory page for updates regarding potential fixes or mitigations.

Description

CVE-2026-133225 is a moderate severity vulnerability in the Red Hat build of Keycloak involving improper verification during User-Managed Access (UMA) token requests. The flaw allows an authenticated user to obtain valid Requesting Party Tokens (RPTs) for clients or resource servers that have been administratively disabled, bypassing intended access controls. However, the issued tokens do not grant privileges beyond those already authorized for the user. The impact is limited in typical deployments where downstream services enforce online token introspection or client status verification. No official fix or mitigation meeting Red Hat's criteria is currently available.

References

Community reviews

Loading reviews…