Keycloak Auth Bypass via Consent Endpoint without Session Code
CVE-2026-133221 Published on November 19, 2026
Org.keycloak.authentication: pending required actions (e.g. configure_totp) can be bypassed via post to login-actions/consent without a valid session_code
A flaw was found in Keycloak. An authenticated remote user with a pending required security action, such as configuring multi-factor authentication (MFA), can bypass the mandatory action by submitting a specially crafted request to the consent endpoint without a valid session code. Keycloak incorrectly interprets the submission as a page refresh and completes the authentication process, allowing the user to access the application without fulfilling the required security policies.
Vulnerability Analysis
CVE-2026-133221 can be exploited with network access, and requires small amount of user privileges. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have a small impact on confidentiality and integrity, and no impact on availability.
Timeline
Reported to Red Hat.
Made public.
Weakness Type
Improper Enforcement of Behavioral Workflow
The software supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence.
Products Associated with CVE-2026-133221
stack.watch emails you whenever new vulnerabilities are published in Red Hat Build Keycloak or Red Hat Single Sign On. Just hit a watch button to start following.
Affected Versions
Red Hat Build of Keycloak: Red Hat Build of Keycloak: Red Hat Single Sign-On 7: Red Hat Single Sign-On 7:Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.