CVE-2026-1486
JWT Authorization Bypass in Keycloak Due to Disabled IdP Check
Publication date: 2026-02-09
Last updated on: 2026-02-10
Assigner: Red Hat, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| keycloak | keycloak | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-358 | The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Keycloak's jwt-authorization-grant flow. The server does not verify whether an Identity Provider (IdP) is enabled before issuing tokens. Specifically, the mechanism that looks up the IdP configuration does not check if the IdP is disabled. As a result, even if an administrator disables an IdP (for example, due to compromise or offboarding), an attacker who has the IdP's signing key can still create valid JWT assertions. Keycloak will accept these assertions and issue valid access tokens.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access because an attacker with the signing key of a disabled Identity Provider can generate valid access tokens. These tokens can be used to gain access to protected resources or services, potentially leading to data breaches, privilege escalation, and other security incidents.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know