# CVE-2026-112208: Keycloak authentication bypass in organization identity-first login

Source: https://junglewise.ai/threats/cve-2026-112208-a-flaw-was-found-in-the-organization-identity-first-login-flow  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-05. Updated: 2026-11-05  
License: CC BY 4.0 with a link back

CVE-2026-112208 · Severity: high · CVSS 8.1 · Published 2026-11-05

Keycloak is an open-source identity and access management system that secures applications and services. A flaw in its organization identity-first login feature allows attackers who belong to multiple organizations to bypass authentication and take over victim accounts. This grants the attacker full access to the victim's account and all connected applications.

Technologies: [Red Hat Keycloak](https://junglewise.ai/threats/technologies/red-hat-keycloak). Vendors: [Red Hat](https://junglewise.ai/threats/vendors/red-hat).

## Quick answers

**Is CVE-2026-112208 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-112208 being exploited in the wild.

**How severe is CVE-2026-112208?** High severity, with a CVSS score of 8.1, published 5 November 2026.

**Which products and versions are affected?** Red Hat Keycloak.

**Is there a fix for CVE-2026-112208?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-112208 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-112208?** Check whether you run Red Hat Keycloak. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability stems from improper handling of an internal authentication state flag (SSO_AUTH) during login flow transitions. When an authenticated user in multiple organizations initiates a registration or password reset flow, the flag is not cleared from the session. An attacker can then supply a victim's username, and the system incorrectly treats the stale flag as proof of the victim's identity, bypassing authentication. This is a CWE-305 authentication bypass requiring network access and low privileges (attacker must have organization membership).

## Affected products

- Red Hat Keycloak

## Timeline

- 2026-11-05: disclosed

## References

- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)
- [https://access.redhat.com/security/cve/CVE-2026-112208](https://access.redhat.com/security/cve/CVE-2026-112208)

## Related threats

- [Red Hat Keycloak missing authorization check in group reparenting](https://junglewise.ai/threats/cve-2026-116468-a-flaw-was-found-in-the-group-move-and-organization-group)
- [Keycloak privilege escalation via client authentication manipulation](https://junglewise.ai/threats/cve-2026-9797-a-flaw-was-found-in-keycloak-s-administrative-services-org)
- [Keycloak Account REST API session manipulation](https://junglewise.ai/threats/cve-2026-97367-a-flaw-was-found-in-the-keycloak-account-rest-api-where-it)
- [Keycloak token exchange lifetime bypass in Standard Token Exchange V2](https://junglewise.ai/threats/cve-2026-96460-a-flaw-was-found-in-the-token-exchange-mechanism-of-keycloak-when)
- [Keycloak SAML broker ProxyRestriction bypass](https://junglewise.ai/threats/cve-2026-92856-a-flaw-was-found-in-the-saml-brokering-component-of-keycloak-an)