CVE-2026-3429: Org.keycloak.services.resources.account: improper access control leading to mfa deletion and account takeover in keycloak account rest api

Published Mar 2, 2026
·
Updated

A flaw was identified in the Account REST API of Keycloak that allows a user authenticated at a lower security level to perform sensitive actions intended only for higher-assurance sessions. Specifically, an attacker who has already obtained a victim’s password can delete the victim’s registered MFA/OTP credential without first proving possession of that factor. The attacker can then register their own MFA device, effectively taking full control of the account. This weakness undermines the intended protection provided by multi-factor authentication.

Other sources

Improper Access Control vulnerability in the Account REST API of Keycloak. The flaw is caused by insufficient validation of the authentication Level of Assurance (LoA) before allowing credential management actions. An attacker who has obtained a victim’s primary credentials (username and password) can authenticate at a lower LoA and delete the victim’s registered OTP/MFA credential without completing step-up authentication. The attacker can then register their own MFA device, effectively achieving full account takeover. Exploitation requires network access and valid credentials but no user interaction, resulting in compromise of account integrity and partial confidentiality impact.

Red Hat

Affected Software

3 affected components
Keycloak Keycloak
maven/org.keycloak:keycloak-services<=26.5.5
redhat Build Of Keycloak>=26.4<26.4.11

Event History

Mar 2, 2026
Data Sourced
via Red Hat·10:03 AM
DescriptionSeverityAffected Software
Mar 11, 2026
CVE Published
via MITRE·04:17 PM
Data Sourced
via MITRE·04:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
Affected Software
Advisory Published
via GitHub·06:30 PM
Data Sourced
via GitHub·06:30 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-3429?

CVE-2026-3429 is classified as a critical severity vulnerability that allows for improper access control, potentially leading to account takeover.

2

How do I fix CVE-2026-3429?

To mitigate CVE-2026-3429, upgrade Keycloak to version 26.5.6 or later, which addresses the access control vulnerability.

3

What type of vulnerability is CVE-2026-3429?

CVE-2026-3429 is an improper access control vulnerability affecting the Keycloak Account REST API.

4

What actions are impacted by CVE-2026-3429?

CVE-2026-3429 allows users authenticated at lower security levels to delete multi-factor authentication settings and perform sensitive actions.

5

What software versions are affected by CVE-2026-3429?

CVE-2026-3429 affects Keycloak versions up to and including 26.5.5.

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