CVE-2026-133221: Org.keycloak.authentication: pending required actions (e.g. configure_totp) can be bypassed via post to login-actions/consent without a valid session_code

Published Nov 19, 2026
·
Updated

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.

Other sources

After completing the first auth factor (password), a user with pending required action (e.g. CONFIGURETOTP) can bypass it by sending POST to /login-actions/consent with valid tabid but without/arbitrary sessioncode. Endpoint treats it as page refresh, auth completes without required action.

— Red Hat

Affected Software

1 affected component
Red Hat Keycloak

Event History

Nov 19, 2026
Data Sourced
via Red Hat·03:48 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·05:55 PM
Data Sourced
via MITRE·05:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated remote user who has completed the first authentication factor and has a pending required action can exploit it. The user needs a valid tab_id for the authentication flow; the session_code may be omitted or arbitrary.

2

Which security controls can be bypassed?

Required actions that must be completed after initial authentication can be bypassed, including CONFIGURE_TOTP. This can allow access to an application without completing the configured mandatory security policy.

3

Does exploitation require user interaction or elevated privileges?

No user interaction is required. The affected user needs low-level authenticated access: they must be able to complete the first authentication factor and reach a flow with a pending required action.

4

How is the bypass performed?

The attacker submits a specially crafted POST request to /login-actions/consent with a valid tab_id and no valid session_code. Keycloak treats the request as a page refresh and completes authentication rather than enforcing the pending action.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203