🔒 Keycloak 26.8.2 Is Now Available: 33 Security Fixes
- keycloak
- security
- upgrade
- Improvement
Keycloak 26.8.2 was published on 5 November 2026 and is now generally available on Cloud-IAM for every deployment running Keycloak 26. It's a security release, so we recommend upgrading at the next opportunity rather than waiting for your usual cycle.
What this release fixes
26.8.2 closes 33 vulnerabilities (CVEs) present in every earlier version. Two of them are rated critical: a signature bypass on the SAML HTTP-Redirect binding (CVE-2026-117691) and a flaw in the Brotli4j library (CVE-2026-111497, not reachable in the Cloud-IAM configuration). The batch also includes four denial-of-service issues exploitable without authentication and three account-takeover scenarios. Keycloak Advisor now lists the 33 CVEs on any deployment still running 26.8.1 or earlier.
No downtime, no sign-in lost
The upgrade from 26.8.x is a rolling upgrade, one node at a time: we confirm there is no downtime, and user sessions are kept, so nobody has to sign in again (unless you have disabled the persistent user sessions feature on your deployment, in which case sessions only live in memory). Expect 15 to 20 minutes end to end, with a backup taken before the first node moves.
Changes to check before you upgrade
This release also closes historical tolerances in Keycloak: 14 behaviour changes in all. Two of them can affect most integrations, the others apply to specific setups.
Admin REST API clients of your own need the kc-admin-api scope. Keycloak now requires access tokens used against the Admin REST API to carry a dedicated audience, provided by a new built-in client scope named kc-admin-api. The upgrade assigns it to the built-in admin-cli and security-admin-console clients, so the admin console and the kcadm CLI keep working, and so does the Keycloak MCP server provided by Cloud-IAM, whose clients we take care of. If you call the Admin REST API with your own client or service account (Terraform provider, provisioning scripts, custom tooling), assign the kc-admin-api client scope to that client as a default client scope before or right after the upgrade. If you prefer to keep it optional, every token request must ask for it explicitly with scope=openid kc-admin-api. Until then those calls return 401 Unauthorized.
Protocol mappers now require realm management rights. Creating, updating or deleting protocol mappers on clients or client scopes through the Admin REST API now requires permission to manage the realm. A delegated administrator who only manages clients can't edit mappers anymore unless you list the allowed mapper types in Realm settings, under "Allowed protocol mapper types for client administrators". The same list limits the mappers accepted through Dynamic Client Registration.
For SAML setups: the SAML identity broker now rejects assertions without a valid bearer SubjectConfirmation or carrying a ProxyRestriction condition, applications using the Keycloak SAML adapter must have the real realm URL as entityID in keycloak-saml.xml instead of the old idp placeholder (re-download the adapter configuration from the client's Installation tab), and SAML SOAP requests are capped at 120 KB.
A few more changes apply to specific setups: Dynamic Client Registration can no longer set default roles or full scope, identity provider auto-linking requires Trust Email when the provider does not verify emails, tokens from the standard token exchange no longer outlive the subject token, and domain-based organization membership requires a verified email. The complete list, with what each change means for a Cloud-IAM deployment, is in our Keycloak upgrades reference: https://documentation.cloud-iam.com/references/keycloak-upgrades.html#patch-releases-of-the-26-8-line
Getting started
Open your deployment in the console, click Pilot, then Upgrade. Pick 26.8.2 in the dropdown, choose As Soon As Possible or Next maintenance window, then Next Steps and Apply. If your deployment has custom extensions, check their compatibility first. The Cloud-IAM extensions from the marketplace are compatible with 26.8.2.
Deployments whose Security Center policy is set to Upgrade immediately or Notify, then upgrade are upgraded by Cloud-IAM in their next maintenance window. With Require my approval, the upgrade waits for you, and the deployment stays exposed in the meantime.
Prerequisites
Dedicated deployment on Keycloak 26.x. Freemium deployments are upgraded by Cloud-IAM without notice.
If you're unsure whether one of these changes applies to you, contact us and we'll check your configuration with you.