CVE-2026-9087: Authorization Bypass Through User-Controlled Key in Red Hat Red Hat Build of Keycloak
A flaw was found in Keycloak. The cross-session verification proof is keyed only by (local userId, idpAlias) and is not bound to the upstream identity that was actually verified, so a second upstream account on the same IdP can consume it and get linked to the victim's local account.
AI Analysis
Technical Summary
The vulnerability in Red Hat Build of Keycloak involves an authorization bypass through a user-controlled key. Specifically, the cross-session verification proof uses only (local userId, idpAlias) as the key and does not bind to the upstream identity that was verified. Consequently, a second upstream account on the same IdP can reuse the verification proof to link to the victim's local account, bypassing intended authorization controls. This flaw affects the integrity and confidentiality of user account linking within Keycloak.
Potential Impact
An attacker controlling a second upstream account on the same identity provider can exploit this flaw to link their account to another user's local account in Keycloak. This compromises the integrity and confidentiality of user account associations, potentially allowing unauthorized access to resources or data linked to the victim's account. There is no reported impact on availability. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-9087 for current remediation guidance. No official fix or temporary workaround is indicated in the advisory content provided. Users should monitor the vendor advisory for updates and apply patches promptly once available.
CVE-2026-9087: Authorization Bypass Through User-Controlled Key in Red Hat Red Hat Build of Keycloak
Description
A flaw was found in Keycloak. The cross-session verification proof is keyed only by (local userId, idpAlias) and is not bound to the upstream identity that was actually verified, so a second upstream account on the same IdP can consume it and get linked to the victim's local account.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Red Hat Build of Keycloak involves an authorization bypass through a user-controlled key. Specifically, the cross-session verification proof uses only (local userId, idpAlias) as the key and does not bind to the upstream identity that was verified. Consequently, a second upstream account on the same IdP can reuse the verification proof to link to the victim's local account, bypassing intended authorization controls. This flaw affects the integrity and confidentiality of user account linking within Keycloak.
Potential Impact
An attacker controlling a second upstream account on the same identity provider can exploit this flaw to link their account to another user's local account in Keycloak. This compromises the integrity and confidentiality of user account associations, potentially allowing unauthorized access to resources or data linked to the victim's account. There is no reported impact on availability. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-9087 for current remediation guidance. No official fix or temporary workaround is indicated in the advisory content provided. Users should monitor the vendor advisory for updates and apply patches promptly once available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2026-05-20T14:53:18.352Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-9087","vendor":"Red Hat"}]
Threat ID: 6a0de26eba1db473628f2ece
Added to database: 5/20/2026, 4:33:50 PM
Last enriched: 5/20/2026, 4:49:08 PM
Last updated: 5/20/2026, 6:42:11 PM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.