CVE-2026-1486: Org.keycloak.protocol.oidc.grants: disabled identity providers are still accepted for jwt authorization grant

Published Jan 27, 2026
·
Updated

A flaw was found in Keycloak. A vulnerability exists in the jwt-authorization-grant flow where the server fails to verify if an Identity Provider (IdP) is enabled before issuing tokens. The issuer lookup mechanism (lookupIdentityProviderFromIssuer) retrieves the IdP configuration but does not filter for isEnabled=false. If an administrator disables an IdP (e.g., due to a compromise or offboarding), an entity possessing that IdP's signing key can still generate valid JWT assertions that Keycloak accepts, resulting in the issuance of valid access tokens.

Affected Software

3 affected componentsFixes available
Keycloak Keycloak
maven/org.keycloak:keycloak-services<26.4.9
26.4.9
maven/org.keycloak:keycloak-services>=26.5.0<26.5.3
26.5.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.keycloak:keycloak-services to a version that resolves this vulnerability.

    Fixed in 26.4.9
  2. Upgrade

    Upgrade maven/org.keycloak:keycloak-services to a version that resolves this vulnerability.

    Fixed in 26.5.3
  3. Configuration

    Update Keycloak behavior for the jwt-authorization-grant flow so that the issuer lookup mechanism (lookupIdentityProviderFromIssuer) rejects IdPs where isEnabled=false; disabled identity providers must not be accepted for jwt authorization grant token issuance.

    Keycloak jwt-authorization-grant issuer lookup (lookupIdentityProviderFromIssuer) = Filter out disabled Identity Providers (isEnabled=false) before issuing tokens

Event History

Jan 27, 2026
Data Sourced
via Red Hat·01:37 PM
DescriptionSeverityAffected Software
Feb 9, 2026
CVE Published
via MITRE·06:36 PM
Data Sourced
via MITRE·06:36 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·09:31 PM
Data Sourced
via GitHub·09:31 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-1486?

CVE-2026-1486 is classified as a high severity vulnerability due to improper validation of identity providers in jwt authorization grants.

2

How do I fix CVE-2026-1486?

To fix CVE-2026-1486, ensure that only enabled identity providers are allowed to issue tokens by applying configuration changes or patches provided by Keycloak.

3

What versions of Keycloak are affected by CVE-2026-1486?

CVE-2026-1486 affects all versions of Keycloak that do not have the necessary updates to validate the enabled status of identity providers.

4

What impact does CVE-2026-1486 have on security?

CVE-2026-1486 can lead to unauthorized access by accepting tokens from disabled identity providers, compromising the security of applications relying on Keycloak.

5

Is there a workaround for CVE-2026-1486?

A temporary workaround for CVE-2026-1486 is to manually disable any identity providers that should not be used until an official patch is applied.

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