CVE Alert: CVE-2026-112208 – Red Hat

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.

**Risk verdict:** This is a high-impact authentication weakness; KEV, SSVC exploitation status, PoC availability and EPSS are not supplied, so immediate exploitation urgency cannot be confirmed.

**Why this matters:** Successful abuse could expose or alter a victim’s account and provide access to applications relying on the identity service. An attacker may target valuable users to steal data, impersonate them or gain access to connected business systems.

**Most likely attack path:** A remote attacker needs a low-privilege account and the ability to participate in multiple organisations, but no victim interaction is indicated. They can manipulate the identity-first login flow; scope is unchanged, so the flaw does not itself imply a boundary crossing, though the compromised account may unlock connected applications.

**Who is most exposed:** Organisations using multi-organisation identity deployments and identity-first login, especially where one identity service protects many applications, should assess exposure first.

Review authentication events where one session switches from login to registration or password reset.

Alert on successful access after an organisation change or unusual username substitution.

Correlate identity-provider sessions with unexpected access to connected applications.

Check logs for repeated failed or abandoned login flows followed by successful account access.

Mitigation and prioritisation

Confirm affected deployments and apply the vendor’s fixed update promptly; verify the applicable advisory before change approval.

No dependable workaround is identified in the supplied record; restrict access to the login service where feasible.

Review recent account and application activity for suspicious access; reset credentials and revoke sessions if compromise is suspected.

Test the update in a representative environment, then expedite production rollout.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.