REDHAT-BUG-2508308: Medium severity Keycloak Google Identity Provider vulnerability

Published Jul 29, 2026
·
Updated

A Missing Authorization vulnerability was identified in Keycloak Google Identity Provider implementation. The flaw exists in the external access-token exchange code path, which is used when the Token Exchange V1 feature is enabled. While the standard Google ID-token login flow correctly validates the hd hosted domain claim against the configured hostedDomain setting, the access-token exchange flow skips this validation. When an external access token is provided, Keycloak retrieves the user profile from the Google user-info endpoint but fails to verify that the domain associated with the user matches the restricted domain configured in the Identity Provider settings. An attacker with a valid Google access token for any domain can exploit this flaw if they have access to a confidential client authorized to perform token exchange. Successful exploitation allows the attacker to bypass domain restrictions, obtain a Keycloak access token, and potentially create or link a brokered identity that should have been restricted.

Affected Software

1 affected component
Keycloak Google Identity Provider

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Disable the Token Exchange V1 feature in Keycloak so the external access-token exchange code path (used for access-token exchange) is not reachable.

    Keycloak Google Identity Provider (external access-token exchange / Token Exchange V1) Token Exchange V1 feature = disable
  2. Configuration

    Ensure Keycloak validates that the domain (hosted domain) associated with the Google user profile returned from the user-info endpoint matches the restricted/hosted domain configured in the Identity Provider settings (the access-token exchange flow currently skips this validation).

    Keycloak Google Identity Provider Identity Provider restricted domain verification = required

Event History

Jul 29, 2026
Data Sourced
via Red Hat·08:40 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-2508308?

The severity of REDHAT-BUG-2508308 is medium, with a score of 4.

2

What is the risk associated with REDHAT-BUG-2508308?

REDHAT-BUG-2508308 has a risk rating of 19.

3

How do I fix REDHAT-BUG-2508308?

To address REDHAT-BUG-2508308, ensure that the Token Exchange V1 feature is properly configured and managed.

4

What impact does REDHAT-BUG-2508308 have on Keycloak?

REDHAT-BUG-2508308 can lead to unauthorized access due to a missing authorization check in the Google Identity Provider.

5

What component of Keycloak is affected by REDHAT-BUG-2508308?

REDHAT-BUG-2508308 affects the Google Identity Provider implementation in Keycloak.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203