# Keycloak changelog > Open-source identity and access management. - Vendor: Red Hat - Category: Developer Tools - Official site: https://www.keycloak.org - Tracked by: What's New (https://whatsnew.fyi/product/keycloak) - Harvested from: GitHub (keycloak/keycloak) - Entries below: 10 (newest first) What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog. ## Releases ### 26.7.1 - Date: 2026-08-05 - Version: 26.7.1 - Original notes: https://github.com/keycloak/keycloak/releases/tag/26.7.1 - Permalink: https://whatsnew.fyi/product/keycloak/releases/26.7.1 - **security** — JWE request object bypasses requestObjectSignatureAlg enforcement - **security** — Privilege escalation via hardcoded role mapper injection in manage-clients - **security** — Keycloak Admin UI Extension brute-force-user User Disclosure via search=id: under FGAP v2 - **security** — Fine-Grained Admin Permissions Bypass in Client Scope Assignment - **security** — FGAP v2 parent group children endpoint bypasses per-child view permission filter - **fixed** — WebAuthn authenticator attachment policy is bypassed when the client omits the attachment field - **fixed** — New Password is committed when multiple Password Reset is detected - **fixed** — 500 error when client requests organization scope with it already set to Default - **fixed** — IllegalFormatConversionException in LiquibaseDBLockProviderFactory and wrong time conversion
Before upgrading refer to the migration guide for a complete list of changes.
oidcadmin/apiadmin/fine-grained-permissionsadmin/fine-grained-permissionsadmin/fine-grained-permissionsauthentication/webauthncioperatorauthenticationauthenticationcoreThis release features new capabilities for users and administrators of Keycloak. The highlights of this release are:
Automate user provisioning with the SCIM API (preview)
Simplified multi-cluster high availability without external caches (preview)
Enhanced reverse proxy guides with blueprints for HAProxy and Traefik
Step-up authentication for SAML clients
Read on to learn more about each new feature. If you are upgrading from a previous release, also review the changes listed in the upgrading guide.
The Identity Brokering API allows applications to retrieve tokens obtained from external identity providers during federated login. Version 2 of this API replaces the legacy V1 with a more secure and standards-compliant design:
Client-level authorization — access to external tokens is controlled per client using dedicated settings (Allow retrieve external tokens and an identity provider allow list) instead of assigning broker roles to individual users.
Confidential clients only — public clients are rejected, ensuring that only authenticated clients can retrieve external tokens.
OAuth 2.0 compliant — the endpoint uses POST and returns standard JSON responses with access_token, error, and error_description fields.
Session-based token storage — a new Store token in session option keeps tokens in the user session for faster access, with automatic cleanup on session expiry. Database storage remains available for persistence across sessions.
V2 is now supported but disabled by default. V1 is deprecated but still enabled by default for backward compatibility. In a future release, V1 will be removed and V2 will become the default.
For more information, see the Identity Brokering APIs chapter in the Server Developer Guide.
Verifiable Credentials (OID4VCI) allow organizations to issue tamper-proof, cryptographically signed credentials — such as employee badges, academic diplomas, or professional certifications — that users can store in a digital wallet and present to third parties without involving the issuer.
OID4VCI remains an experimental feature in Keycloak, but this release brings substantial improvements from both the core team and the community:
Polishing of existing functionality and improving configuration. Everything is now configurable in the admin UI in addition to the admin REST API.
Lots of bugs fixed. Improved specification compliance.
Conformance with the OpenID4VC High Assurance Interoperability Profile (HAIP). This _[Truncated at 4000 characters — full notes: https://github.com/keycloak/keycloak/releases/tag/26.7.0]_ ### 26.6.4 - Date: 2026-06-26 - Version: 26.6.4 - Original notes: https://github.com/keycloak/keycloak/releases/tag/26.6.4 - Permalink: https://whatsnew.fyi/product/keycloak/releases/26.6.4 - **security** — Fix group-admin escalation to realm-admin vulnerability - **security** — Fix information disclosure through arbitrary filesystem path probing vulnerability - **security** — Fix cross-site scripting (XSS) via case-insensitive URI validation bypass vulnerability - **security** — Fix attacker ability to re-enable and take over disabled clients via registration access token - **security** — Fix privilege escalation via improper scope mapping enforcement vulnerability - **security** — Fix unauthorized access to resources via UMA permission ticket bypass vulnerability - **security** — Fix policy enforcer authorization bypass via incorrect URI comparison vulnerability - **security** — Fix authentication bypass via JWT algorithm confusion vulnerability - **changed** — Upgrade to Quarkus 3.33.2.1
Before upgrading refer to the migration guide for a complete list of changes.
Before upgrading refer to the migration guide for a complete list of changes.
account/uioidcauthorization-servicesaccount/apioidcauthentication/webauthnadmin/fine-grained-permissionsidentity-brokeringoidcsamlorganizationsadmin/apildapoidcoidcoidcauthorization-servicesBefore upgrading refer to the migration guide for a complete list of changes.
authorization-servicesorganizationscoreauthentication/webauthncoreBefore upgrading refer to the migration guide for a complete list of changes.
corecoretestsuitetestsuiteoidccioperatoradmin/client-javaadmin/client-jsadmin/uiorganizationsadmin/uiidentity-brokeringdocsdist/quarkusThis release features new capabilities for users and administrators of Keycloak. The highlights of this release are:
JWT Authorization Grant, enabling external-to-internal token exchange using externally signed JWT assertions.
Federated client authentication, eliminating the need to manage individual client secrets in Keycloak.
Workflows, enabling administrators to automate realm administrative tasks such as user and client lifecycle management.
Zero-downtime patch releases, allowing rolling updates within a minor release stream without service downtime.
The Keycloak Test Framework, replacing the previous Arquillian-based solution.
All of these features are now fully supported and no longer in preview. Read on to learn more about each new feature. If you are upgrading from a previous release, also review the changes listed in the upgrading guide.
JWT Authorization Grant (RFC 7523) is designed to implement external-to-internal token exchange use cases. This grant allows using externally signed JWT assertions to request OAuth 2.0 access tokens.
In this release, JWT Authorization Grant is promoted from preview to supported. See the JWT Authorization Grant guide for additional details.
Federated client authentication allows clients to leverage existing credentials once a trust relationship with another issuer exists. It eliminates the need to assign and manage individual secrets for each client in Keycloak.
Federated client authentication is now promoted to supported, including support for client assertions issued by external OpenID Connect identity providers and Kubernetes Service Accounts.
Since the OAuth SPIFFE Client Authentication specification is still in draft status, this feature remains a preview feature in Keycloak.
A new guide for OAuth 2.0 Demonstrating Proof-of-Possession (DPoP) in the Securing applications Guides provides information on how to mitigate the risk of stolen tokens by making tokens sender-constrained.
See Securing applications with DPoP for more details.
A new preview version 2 for the Identity Brokering APIs is introduced in this release. When brokering is used during the authentication process, Keycloak allows you to store tokens and responses issued by the external Identity Provider. Applications can call a specific endpoint to retrieve those tokens, which, in turn, can be used to get extra user information or invoke endpoints in the external trust domain. The new version improves the token retrieval endpoint to substitute the internal to external Token Exchang _[Truncated at 4000 characters — full notes: https://github.com/keycloak/keycloak/releases/tag/26.6.0]_ ### 26.5.7 - Date: 2026-04-02 - Version: 26.5.7 - Original notes: https://github.com/keycloak/keycloak/releases/tag/26.5.7 - Permalink: https://whatsnew.fyi/product/keycloak/releases/26.5.7 - **security** — Fix improper access control in Admin REST API that leads to information disclosure - **security** — Fix static handler component cache manipulation vulnerability in vertx-core that can deny access to static files - **security** — Fix improper access control for level of assurance during credential deletion in account API - **security** — Fix application-level denial of service vulnerability via scope processing - **security** — Fix UMA policy resource injection vulnerability that allows unauthorized cross-user permission grants - **security** — Fix redirect URI validation bypass via path traversal in OIDC auth endpoint - **security** — Fix privilege escalation vulnerability via forged authorization codes due to SingleUseObjectProvider isolation flaw - **changed** — Upgrade to Quarkus 3.27.3 - **fixed** — Fix uncaught error when call is made without Host header
Before upgrading refer to the migration guide for a complete list of changes.
admin/apiaccount/apidist/quarkuscoreBefore upgrading refer to the migration guide for a complete list of changes.
oidcoidccoreuser-profileorganizationsstorageauthenticationadmin/apioidcoperatorldapcoredocsinfinispantoken-exchangeorganizations