Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
4.2
Keycloak: Attacker Can Delete MFA and Take Over Accounts
CVE-2026-3429
GHSA-8g9r-9wjw-37j4
Summary
A security flaw in Keycloak's Account REST API allows an attacker with a victim's password to delete their MFA/OTP credential, then register a new MFA device, gaining full control of the account. This bypasses the intended security of multi-factor authentication. Keycloak users should review their account security settings and consider updating their MFA methods to prevent unauthorized access.
What to do
No fix is available yet. Check with your software vendor for updates.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| – | org.keycloak:keycloak-services | <= 26.5.5 | – |
Original title
Keycloak: Improper Access Control Leading to MFA Deletion and Account Takeover in Keycloak Account REST API
Original description
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.
nvd CVSS3.1
4.2
Vulnerability type
CWE-284
Improper Access Control
Published: 11 Mar 2026 · Updated: 13 Mar 2026 · First seen: 11 Mar 2026