CVE-2026-1609: Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users

Published Jan 29, 2026
·
Updated

A flaw was found in Keycloak. When the JSON Web Token (JWT) authorization grant preview feature is enabled and a user account is disabled, Keycloak fails to validate the user’s disabled status during JWT authorization grant processing. A remote attacker with low privileges can exploit this improper access control vulnerability by presenting a valid assertion token from an external identity provider to obtain a JWT for a disabled user. This allows unauthorized access to sensitive resources.

Other sources

Improper access control vulnerability in the JWT authorization grant preview feature of Keycloak. The issue occurs when the --features jwt-authorization-grant option is enabled, and a user account is disabled. Keycloak fails to validate the user’s disabled status during JWT authorization grant processing. By presenting a valid assertion token from an external identity provider, an attacker can obtain a JWT for a disabled user and use it to access protected endpoints. This can be exploited remotely with low privileges and no user interaction, resulting in unauthorized access to sensitive resources.

Red Hat

Affected Software

2 affected components
Keycloak Keycloak
redhat Build Of Keycloak=26.5.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    If the JWT authorization grant preview feature is not required, disable it (do not run Keycloak with the --features jwt-authorization-grant option), especially when any user accounts are disabled.

    Keycloak --features = jwt-authorization-grant
  2. Compensating control

    Ensure disabled users cannot authenticate via JWT authorization grant processing by disabling the jwt-authorization-grant feature until the underlying access control validation is fixed.

Event History

Jan 29, 2026
Data Sourced
via Red Hat·12:17 PM
DescriptionSeverityAffected Software
Jul 16, 2026
CVE Published
via MITRE·12:26 AM
Data Sourced
via MITRE·12:26 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:16 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-1609?

The severity of CVE-2026-1609 is rated high with a score of 8.1.

2

How do I fix CVE-2026-1609?

To fix CVE-2026-1609, ensure that the JWT authorization grant preview feature is properly configured and consider disabling it if not in use.

3

What type of attack is possible with CVE-2026-1609?

CVE-2026-1609 allows a remote attacker with low privileges to gain unauthorized access to disabled user accounts through JWT authorization.

4

What software is affected by CVE-2026-1609?

CVE-2026-1609 affects the Keycloak and the Red Hat Build of Keycloak.

5

When was CVE-2026-1609 published?

CVE-2026-1609 was published on January 29, 2026.

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