CVE-2026-117627: Keycloak-services: keycloak-services: jwt authorization grant bypasses identity provider login restrictions

Published Oct 27, 2026
·
Updated

A flaw was found in the JWT Authorization Grant implementation of the keycloak-services component. When an OIDC or Google identity provider is configured with specific login restrictions, such as claim filtering, these checks are correctly applied during standard browser logins but are skipped during the JWT-based grant flow. This allows an authenticated client to obtain access tokens for a user even if their identity provider claims should have blocked the login.

Other sources

A vulnerability was found in Keycloak where the JWT Authorization Grant (RFC 7523) fails to enforce login restrictions configured on OIDC or Google identity providers. Specifically, restrictions such as Filtered by claims or Hosted Domain are bypassed when the grant is processed. An authenticated confidential client with the JWT Authorization Grant enabled can submit a signed assertion for an existing federated user and receive realm tokens, even if the assertion contains claims that violate the identity provider's security policies. An attacker with client credentials and a validly signed assertion can bypass intended access controls to obtain unauthorized realm access for federated users.

— Red Hat

Affected Software

1 affected component
Red Hat Keycloak keycloak-services

Event History

Oct 27, 2026
Data Sourced
via Red Hat·01:17 PM
DescriptionSeverityAffected Software
Oct 29, 2026
CVE Published
via MITRE·06:22 AM
Data Sourced
via MITRE·06:22 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Deployments are exposed when they use OIDC or Google identity providers with login restrictions such as claim filtering or Hosted Domain, and have a confidential client with the JWT Authorization Grant enabled. The issue concerns existing federated users whose identity-provider claims would normally prevent login.

2

What does an attacker need to exploit it?

An attacker needs authenticated access as a confidential client, including client credentials, and a validly signed JWT assertion for an existing federated user. No user interaction is required.

3

Which login controls can be bypassed?

The JWT-based grant flow can bypass identity-provider restrictions including Filtered by claims and Hosted Domain. These restrictions remain applied during standard browser logins, but are skipped for the JWT Authorization Grant flow.

4

What is the impact of a successful exploit?

An attacker can obtain realm access tokens for a federated user whose identity-provider claims should have blocked that user from logging in. The stated impact includes unauthorized realm access and low confidentiality and integrity impact.

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