Keycloak-services: keycloak-services: account takeover via stale sso_auth note in organization identity-first login
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The Organization feature is enabled The attacker is a member of at least two organizations The attacker has valid credentials in two or more organizations
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Keycloak identity and access management server is affected by a flaw in its Organization identity-first login flow that lets an attacker take over a victim's account and gain access to the applications connected to it. An attacker can exploit this remotely over the network with low-privilege login (the attacker must hold an account in one of the organizations), and no action by the victim is needed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
A 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Shipped in major Linux distributions
- Severity8.1/10CVSS 8.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
- Would score about 38 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The Organization feature is enabled The attacker is a member of at least two organizations The attacker has valid credentials in two or more organizationsWorkaround: The checked facts list no workaround. Because the bug requires the Organization feature, limiting or disabling that feature removes the precondition, but the facts do not confirm that this fully mitigates the issue.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- keycloak-services
Version range not reported
- rhbk/keycloak-rhel9
Version range not reported
- keycloak-services
Version range not reported
Evidence 2
- Report
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112208
Is CVE-2026-112208 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A stale sso_auth note left in an organization identity-first login flow can let a member of two or more organizations take over a victim's account, including their authorization code, access tokens, and a valid SSO session for downstream applications.Source: access.redhat.com, bugzilla.redhat.com
Am I affected, and how do I check?
The checked facts list Red Hat Build of Keycloak and Red Hat Single Sign-On 7 but give no version ranges. The bug requires the Organization feature to be enabled and an attacker with valid credentials in at least two organizations. To check the setup, look at whether the Organization feature is enabled in the realm settings and which Keycloak version is installed.Source: access.redhat.com, bugzilla.redhat.com
How do I fix CVE-2026-112208?
The checked facts do not name a fixed version, so no upgrade target can be given. Check the Red Hat advisory for the fixed release of your product line and apply it when published.Source: access.redhat.com, bugzilla.redhat.com
What if there's no patch?
The checked facts list no workaround. Because the bug requires the Organization feature, limiting or disabling that feature removes the precondition, but the facts do not confirm that this fully mitigates the issue.Source: access.redhat.com, bugzilla.redhat.com