KEYCLOAK · CVE-2026-112208 · Infrastructure
FIX → 26.8.2 · 26.6.8 ✓ verified
In Keycloak's Organization identity-first login flow, a successful-login flag is not cleared when a user is removed from the session during a switch to registration or password reset. An attacker who belongs to multiple organizations can supply a victim's username and be treated as the victim, gaining full access to the account and connected applications.
first public Nov 5, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Self-hosted Keycloak deployments that use the Organizations feature with the identity-first login flow. An attacker who belongs to more than one organization can start a login, switch to registration or password reset, then supply a victim's username and be treated as that user. Deployments without Organizations can likely skip it, but the Keycloak issue doesn't state that.
Not affected if no-organizations-feature
Who cares keycloak, organizations, self-hosted, sso
26.8.1, so anything below 26.8.2 on the 26.8 line is affected, and the 26.6 line before 26.6.8 is likely affectedA flaw was found in the Organization identity-first login flow of the Keycloak authentication server. Keycloak is an open-source identity and access management solution used to secure modern applications and services. The issue occurs when an attacker who belongs to multiple organizations initiates a login and then switches to a registration or password reset path. During this process, a flag indicating a successful login is not properly cleared when the user is removed from the session. An attacker can then provide a victim's username, and the system incorrectly treats the stale flag as proof of the victim's identity. This allows the attacker to bypass authentication and gain full access to the victim's account and connected applications.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 26.8.2 · 26.6.8
26.8.2 (released 2026-11-05)26.6.8 on the 26.6 line; I did not read a 26.6.8 release pageNVD data is provided by NIST and is public domain. Posts quoted belong to their authors.