Advisory record · GHSA-8g9r-9wjw-37j4

Keycloak: Improper Access Control Leading to MFA Deletion and Account Takeover in Keycloak Account REST API

CVSS 4.2 MediumEPSS 0.0028 · 20th percentile

Published by the GitHub Advisory Database at 11 Mar 2026, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.keycloak:keycloak-servicesMaven<=26.5.6No fixed version yet
Identifiers
GHSA-8g9r-9wjw-37j4 · BIT-keycloak-2026-3429 · CVE-2026-3429
Weakness (CWE)
CWE-284
Published
11 Mar 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Keycloak (org.keycloak:keycloak-services) versions up to and including 26.5.6 are affected. An attacker who already has a victim's password can, without the second factor, delete the victim's registered MFA/OTP credential through the Account REST API, then register their own MFA device and take full control of the account. No fixed version is listed in the source.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.2 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.0028, the 20th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.