Changelog

New features, improvements and fixes to Cloud-IAM, and every Keycloak version as it becomes available on your deployments.

🔒 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.

📖 Read the documentation

Keycloak 26.8.2: critical issues mitigated, update coming

  • advisory
  • security
  • Improvement

Keycloak 26.8.2: the two critical issues are already mitigated on your deployments

Keycloak 26.8.2, released on 5 November 2026, fixes 33 security issues, two of them critical: a SAML redirect-binding signature bypass (CVE-2026-117691, 9.1/10) and an out-of-bounds write in the bundled Brotli decoder (CVE-2026-111497, 9.8/10).

Both are already mitigated on all Cloud-IAM deployments. The SAML attack is blocked by a filtering rule on our load balancers, and the Brotli flaw is not reachable in the configuration we run, since the vulnerable decoder is only used by an experimental feature that no deployment enables. We are not aware of any active exploitation.

We are now reviewing the remaining issues against each deployment's configuration and will contact the organisations whose setup is exposed. Keycloak 26.8.2 will be available in your console in the coming days, with details on the behaviour changes it ships (notably an audience check on the Admin REST API) and the upgrade options.

No action is required on your side at this stage.

Choose How We Handle CVEs on Your Deployments 🛡️

  • security
  • Feature

When a security vulnerability is published for Keycloak, the right response depends on your deployment. Some teams want the fix applied right away, others need to plan the upgrade around their own releases. You can now tell us which approach you prefer, from the new Security Center in the console.

CVE upgrade policy

For each deployment, you decide how Cloud-IAM proceeds when a CVE affects it. You set the policy separately for Critical severity CVE and High severity CVE, and pick one of three modes:

  • Upgrade immediately: we upgrade your deployment without prior notice.
  • Notify, then upgrade: we notify you first, then upgrade.
  • Require my approval: we wait for your approval before upgrading.

For example, you can let us upgrade a staging deployment immediately and require your approval for production.

Getting started

Open a deployment and go to the Security Center tab. In CVE upgrade policy, select a mode for each severity, then click Save changes. Each severity shows whether it uses your Plan default or has been Customized.

Prerequisites

  • Only the owners of a deployment can change its policy. Other members can view it.
  • Some settings may be marked Fixed by plan or Fixed by contract. A setting fixed by your contract can only be changed by contacting Cloud-IAM.
  • The CVE upgrade policy isn't available on free plans.

This is the first step in improving how we manage CVEs and the upgrades they lead to. More will follow in the Security Center.

eMudhra CA compromise: your Keycloak is already patched, low risk for the services it connects to

  • advisory
  • security
  • Information

In October 20, 2026, eMudhra disclosed that several of its intermediate certificate authorities had been issued with weak private keys (CVE-2026-114406). Browsers and Linux distributions have stopped trusting the roots above them, so your security team may ask whether your Keycloak deployments are affected.


What was affected
The Java truststore shipped in the Keycloak images still trusted three emSign roots: emSign ECC Root CA - G3, emSign ECC Root CA - C3 and emSign Root CA - C1. This truststore is used only for the outbound TLS connections Keycloak makes itself, for example to an external identity provider, an LDAP directory or an SMTP server. The certificates your users see when they connect to your instances aren’t involved.
Exploiting this would require both a position on the network path between your Keycloak and one of those services, and a certificate issued from a compromised key. We consider the risk low, and we’ve removed the roots anyway.


What we did
We rebuilt the Keycloak images of every version still under maintenance without the three affected roots. emSign Root CA - G1 wasn’t affected and stays trusted, as it does in Mozilla’s and Red Hat’s trust stores.
Before removing them, we checked every identity provider, LDAP directory and SMTP server configured on your deployments and reachable from our infrastructure. None of them relies on the removed roots, so no existing connection should break.
Your deployments switch to the updated image as they’re redeployed during their usual maintenance window. Your Keycloak version and configuration stay the same.


What you need to do
Nothing, in most cases. If one of your services sits on a private network we couldn’t reach, or if you add a new connection later, make sure its certificate isn’t issued by eMudhra (emSign). If it is, contact us. That certificate needs to be replaced anyway, since eMudhra has revoked the compromised intermediates.

If your security team needs a written statement for their records, contact us and we’ll provide it.

PHP2Shell: Your Keycloak deployments are not affected and remain safe

  • advisory
  • security
  • Information

No PHP anywhere, so nothing to patch

On 21 October 2026 the PHP project shipped emergency fixes for two critical remote code execution flaws, CVE-2026-109618 and CVE-2026-109619, known together as PHP2Shell. Exploitation attempts have already been observed in the wild, so your security team may ask whether your Keycloak deployments are exposed.

They are not. We reviewed every component we run for you and every component of the Cloud-IAM platform. None of them executes PHP or ships a PHP interpreter.

There is no upgrade to schedule and no mitigation to apply on your side for this advisory. Your deployments stay on their usual maintenance schedule.

One side effect of the announcement is more opportunistic scanning for PHP paths (.php files, phpMyAdmin and the like). Your load balancers already ban those sources automatically with fail2ban after two attempts in a minute, so that noise never reaches Keycloak.

If your security team needs a written statement for their records, contact us and we'll provide it.

Keycloak 26.8.0 is now available on Cloud-IAM

  • Keycloak release

Keycloak 26.8.0 is validated and available on all Cloud-IAM deployments. SCIM provisioning, client secret rotation with a grace period, and stateless multi-cluster (v2) are now production-ready. OID4VCI, parameterized scopes, token exchange delegation and the Client Admin API v2 arrive as preview features.

Three security fixes change existing behaviour: identity provider mappers no longer grant admin roles unless allowAdminRoleMapping is enabled, bare group names in claims resolve to top-level realm groups only, and disabled clients are dropped from the token audience. Check these before upgrading.

Upgrade from Pilot → Upgrade in the console. No downtime from 26.7.x, 15 to 20 minutes, backup taken automatically. Supported until the end of October 2027.

📖 Read the documentation

The AD Agent Now Syncs Your Groups and Protects Your Accounts

  • ad-agent
  • Feature

Your Active Directory groups now appear on your users

The groups an account belongs to in your directory can now be carried into Keycloak, so you no longer have to recreate them by hand and keep them in step.

It is off by default and enabled in your User Federation entry, where you also choose how far it goes. Add memberships only and never remove any. Align Keycloak on your directory, removals included. Or report, which brings the memberships in and merely logs the removals it would make, so you can see the effect on your real data before letting it act. Groups you created yourself in Keycloak are never touched, in any mode, and neither are the memberships you granted in them.

The AD Agent guide walks through the fields to set and the behaviour of each mode.

This comes with a new version of the connector. We update your deployment without interruption of service, and you pull the latest agent image on your side.

  • ad-agent
  • resiliency
  • Fix

A directory outage no longer costs you accounts

A network outage, a restarting agent or a domain controller slow to answer was read as "this user no longer exists", and the Keycloak account was deleted, taking its group memberships, its roles and its attributes with it. Nothing warned you, and an account recreated afterwards came back empty.

A directory that cannot answer is never treated as an absence any more. Removing accounts your directory positively reports as gone has become a setting of its own, which is off unless you turn it on.

  • ad-agent
  • Improvement

The user search shows each account once, and every page

Accounts were listed twice, once as imported in Keycloak and once as returned by your directory. Paging was worse: the second page repeated the first, which put every account beyond it out of reach from the console.

Both are fixed, and searches are now restricted to the population you configured, so computer accounts stop showing up among your users.

  • ad-agent
  • resiliency
  • Fix

Renaming a user in your directory keeps their Keycloak account

An account was recognised by its login name, so a rename created a second, empty account while the original one was discarded with its groups and its roles.

Accounts are now matched on the identifier your directory assigns them for life, so a rename updates the account in place and its history survives.

  • ad-agent
  • resiliency
  • Improvement

A silent directory no longer holds your console

An unresponsive directory kept a Keycloak request waiting for 35 seconds, and a large directory was asked to compute results nobody would read.

Searches and logins now have their own ceilings, five and ten seconds by default and both yours to change, and your domain controller is only ever asked for what is needed.

Upgrades Now Tell You Where Your Extensions Stand

  • extensions management system
  • Improvement

A release being validated no longer reads as blocking

The Extension compatibility table has a fourth status: Validating update…

It covers the gap right after a release is created. Until now, the moment a publisher pushed the missing release, the row still said Update required with a Create release button, so there was nothing left to do and no sign that anything was happening. That row now shows Validating update… instead, names the version the extension is moving to, and drops the button. Hovering the status explains what's running: automated validation, which can take up to 15 minutes.

You don't have to reload to find out how it went. The console keeps watching the release, and the row turns into Update ready by itself once validation passes. The upgrade stays blocked while the release is being validated, and opens up on its own as soon as it succeeds.

  • extensions management system
  • Improvement

The confirmation step says what our validation found

Before, the dialog warned that custom extensions "may not be compatible with the new version" on every deployment carrying one, whatever the state of those extensions. It now reports one verdict for your deployment:

  • Every release validated by our pipeline: a confirmation naming the count and the version, for example "All 2 extensions are validated for 26.7.2".
  • A release validated by hand rather than by our tests: a warning naming the file, plus one more consent so the risk is explicit.
  • No extension of your own installed: nothing about extensions at all.

Every upgrade with extensions also asks you to acknowledge what our validation covers. It's technical, not functional: we check that Keycloak starts with your extension, not that the extension behaves the way your applications expect.

The dialog was tidied up at the same time. Current version, target version with its release notes, schedule, extension verdict and consents are now four clear groups, so the whole decision fits on one screen.

MCP Server for Keycloak

  • ai
  • Beta

Your LLM agents can now talk directly to your IAM. We're introducing a dedicated MCP (Model Context Protocol) server that you can enable per deployment, giving any connected agent structured access to your Keycloak realm.

Query your IAM from your agent
Once enabled, the MCP server exposes around 20 tools covering your Keycloak deployment: realms, clients, users, roles, and more. Your LLM agent can call these tools directly instead of going through the Admin Console or writing custom API calls.

Getting started
Go to your deployment, then Configuration, then Keycloak MCP. A toggle lets you enable it for that deployment.

Prerequisites

  • Premium plan or above
  • Keycloak 26.6 or 26.7

This feature is currently in beta. We'd love your feedback as we expand it.

📖 Read the documentation

Release 27 of August

  • api
  • Fix

"Try it out" now works in the Developer section

You can test any Cloud-IAM API endpoint straight from the console. The interactive API explorer on the Developer page now sends your console session token with every call, so requests are authenticated automatically.

Before, calls made from the page came back with a 401 unless you fetched a token by hand and pasted it into the Authorize dialog. That step is gone: open an endpoint, hit Try it out, and the call runs as you.

Open in the console →
  • api
  • Improvement

Upgrade endpoint accepts a Keycloak version id

PUT /deployments/{deploymentId}/upgrade now accepts either the version id (26.5-quarkus) or the version display name (Keycloak 26.5) in the version parameter. Both forms are returned by GET /marketplace/organizations/{organizationId}/keycloak-versions, so you can pass whichever one your automation already holds.

If the version can't be resolved, the error now lists every accepted value instead of only echoing what you sent, which makes a failing upgrade script far quicker to fix.

  • api
  • documentation
  • Fix

Error responses link to the right documentation page

Every API error carries a documentation link so you can look up what went wrong. Those links pointed to a page that no longer existed and ended on a 404. They now resolve to the deployment lifecycle reference, where the error codes are documented.

See and Raise Your Custom Domain Limit

  • console
  • Feature

Custom domains let your users reach Keycloak on your own hostname. Until now every deployment was capped at a single custom domain, with no way to see where you stood against that cap or to lift it short of a manual request. This release changes both.

See your usage at a glance (new) The Custom domains card now shows your usage right in its title, for example Custom domains (1/3): how many domains are configured against how many your deployment allows. The count only includes domains whose certificate is managed by Cloud-IAM.

Higher limits, set per deployment (new) Your custom domain limit is no longer a fixed value shared by everyone on your plan. It's now a per-deployment setting, so it can be raised for one deployment without touching any other. If you need more than your current limit, contact support and we'll raise it for that deployment.

Getting started Open your deployment, then go to Configuration → Custom domains. The card title shows your current usage and limit, and Register adds a new domain. Once you reach your limit, Register is disabled until the limit is raised.

Prerequisites Custom domains require a dedicated deployment on a plan that includes the feature.

📖 Read the documentation

Release 31 of july

  • ai
  • Beta

🤖 New: Connect Your AI Assistant to Cloud-IAM with MCP

Your Keycloak deployments hold a lot of operational context: audit logs, extension status, billing usage, upcoming upgrades. Getting to it usually means switching to the console. With our new MCP server, you can now ask your AI assistant directly.

Talk to Cloud-IAM from your assistant (new) Cloud-IAM exposes its control plane through the Model Context Protocol, so any MCP-aware client (Claude Desktop, Claude Code, Cursor, and others) can list your deployments, inspect audit logs, check installed extensions, or compute a billing synthesis, straight from a conversation.

Tool calls run with your own identity and permissions, not a shared API key or service account. Every action the assistant takes is logged in the audit trail under your user, the same as if you'd done it from the console.

Nineteen tools, scoped to what you're allowed to see Four organization-scoped tools cover deployment listing, members, service accounts, and billing. Fifteen deployment-scoped tools cover things like deployment detail, plan usage, audit logs, extensions, custom domains, Keycloak feature flags, allow lists, themes, exports, backups, maintenance windows, and pending upgrades. The gateway resolves organizations and deployments by name or ID and only ever against resources you're a member of, so there's no way to reach into an organization or deployment you don't belong to. Note that deployment-scoped tools aren't available for freemium deployments; organization-scoped tools stay available to everyone.

Getting started An ORG_OWNER enables MCP from Settings → MCP in the console, then copies the connection URL that appears below the switch. In Claude, add it as a custom connector under Settings → Connectors → Add custom connector; in Claude Code, run claude mcp add --transport http cloud-iam https://mcp.cloud-iam.com/mcp. The first tool call opens a browser for you to sign in with your usual Cloud-IAM account and grant consent once. Turning the organization switch off immediately revokes access for everyone.

📖 Read the documentation

  • api
  • resiliency
  • Improvement

📈 New: Deployment Availability in the Console and API

Your deployment page has always shown an availability badge, but it was an image loaded from our monitoring provider straight into your browser. That made it something to look at rather than something you could use, and it stopped working whenever the provider was blocked or unreachable. Availability now comes from the Cloud-IAM API.

A clear up or down on your deployment (new)

The Availability row on your deployment summary shows the current state of your instance as a status badge: Up when checks are passing, Down when they're failing, and Maintenance during a maintenance period. The same badge appears on each card in your deployments list. Nothing is fetched from an external provider any more, so the indicator no longer depends on ad blockers or on that provider being up.

Availability from the API (new)

You can read the same state programmatically:

GET /deployments/{deploymentId}/monitoring/uptime

The response is a single status field:

{ "status": "UP" }

Possible values are UP, DOWN, MAINTENANCE, PAUSED, PENDING and VALIDATING. Two more cover the cases where we can't report a live check: UNMONITORED when the deployment has no monitor, and UNKNOWN when the monitoring backend is briefly unreachable. Those two are distinct on purpose, so a hiccup in monitoring never reads as a false outage in your own tooling.

Getting started

Open a deployment and look at the Availability row on the summary page. For the API, call the endpoint above with your usual bearer token. The status refreshes about every 30 seconds, so a change of state shows up shortly after it happens.

Prerequisites

  • A dedicated deployment. Shared plans have no monitor of their own, so they report UNMONITORED.
  • The Owner, Editor or Monitoring role on the organization.
  • console
  • Fix

🔧 Fixed: Reading Product Updates in the Console

Thanks for the first feedback on the release notes feature. Three things made updates awkward to read, and they're all fixed.

Long updates now scroll

The notifications panel capped its height but didn't scroll, so anything below the fold was out of reach. The panel scrolls now, and you can read a release note in full without leaving it.

Wide content stays inside the panel

An update containing a code block or a long unbroken token stretched past the panel and got clipped on the right edge. Text now wraps to the panel width, and code blocks scroll in place.

A way back from the public page

The public Product updates page uses a standalone layout with no navigation, so signed-in readers had no way back. There's now a Back to console link at the top of the page.

Where to find it

Open the bell icon in the top bar for the panel, or View all updates for the full history.

Keycloak 26.7 is now available on Cloud-IAM

  • Keycloak release

Keycloak 26.7 (July 2026) is qualified and ready to deploy. Upgrading from 26.6.x involves no downtime.

Highlights

  • SCIM API (preview): automate user provisioning with full CRUD, PATCH, filtering, and pagination.
  • Identity Brokering API V2: retrieve tokens from external IdPs after federated login. Supported but disabled by default; V1 is now deprecated.
  • Step-up authentication for SAML clients, not just OIDC.
  • OAuth 2.0 for MCP: Keycloak can act as an authorization server for MCP clients.

Worth checking before you upgrade: the view-system admin role is removed, the Twitter IdP is deprecated, DPoP no longer works with implicit/hybrid flows, X509 client auth now needs a CA Subject DN, and token introspection now validates the audience claim.

Dedicated plan customers can upgrade on demand or ask support. A cold backup is taken beforehand.

📖 Read the documentation

Check Your Deployment Status via API

  • api
  • resiliency
  • Feature

Even with a highly available setup, planned maintenance and certain internal processes can temporarily affect the running state of your cluster. If you need to know the state of your deployment at all times, you can now query it directly instead of waiting on status pages or support.

Deployment status endpoint (new)

A new API endpoint returns the current status of your deployment:

GET /deployments/{deploymentId}/monitoring/status

Use it to integrate deployment health into your own monitoring stack, trigger alerts on state changes, or verify that a maintenance window has completed.

Getting started

Call the endpoint with your deployment ID. You can explore the request and response format, and try it live, in our Swagger documentation.

Prerequisites

The endpoint is available to users with the Owner, Editor, or Monitoring role.

📖 Check it in Swagger

Customizable Maintenance Page

  • customization
  • Feature

Even when we work hard to keep your deployment up, downtime can still happen under certain circumstances. Instead of your end users hitting a bare, default error page from the load balancer, Cloud-IAM now lets you customize what they see.

The maintenance page is served to your end users when your Keycloak deployment is temporarily unavailable. It's displayed by the load balancer sitting in front of your deployment, so your users still get a clear response even when no Keycloak server can answer their request. Because it's served by the load balancer and not Keycloak itself, it stays available even when your deployment is fully down.

This covers two situations:

  • During maintenances — when your deployment is briefly down while we apply updates, patches, or infrastructure changes.
  • During incidents — when no Keycloak server is available to handle incoming requests.

You can now choose between three modes:

  • None — the default load balancer response, no custom page.
  • Minimal — a clean, whitelabelled Service unavailable page with a retry button and automatic reconnection. No branding. A good default for most deployments.
  • Custom — your own fully branded page (logo, colors, links, wording) via a self-contained HTML document.

Configure it in the console under Customisation → Maintenance page (Theme section). Note: saving restarts the deployment's load balancer to apply the change, so plan accordingly.

📖 Read the documentation

Customize Your Login Pages and Email Templates

  • customization
  • Feature

Your end users don't just see Keycloak at login. They also receive emails from it, like verification and password reset messages. Now you can make both match your brand, directly from the Cloud-IAM Console, with no code.

Login theming

Our no-code Theme Generator lets you visually customize your Keycloak login pages: accent colors, background color, image or custom CSS for effects like gradients, company logo, favicon, and element shapes. You can preview changes instantly with the WYSIWYG editor, then apply them with a single click. Themes are upgrade-safe, so you design once and Cloud-IAM keeps them compatible with future Keycloak versions. Since Keycloak supports realm-based theming, you can create and manage a distinct branded experience for each realm.

Email templates (new)

You can now apply that same branding to the transactional emails Keycloak sends your users, so the experience stays consistent from the login page to the inbox.

Getting started

Both features live under the Customisation section of the console. For login theming, open the Generator tab, click Create theme, configure it in the visual editor, Save, then Deploy. Changes apply after a 5 to 10 minute rolling upgrade. You then apply the theme per realm from Keycloak's Realm Settings, under Themes.

Prerequisites for login theming: a dedicated Keycloak deployment on a paid plan, the Editor role on your organization, and Keycloak 26.2 or higher.

📖 Read the documentation

Managed Keycloak, Simplified by Cloud-IAM

Focus on your business, we handle the Keycloak

Since 2018, Cloud-IAM has been simplifying Keycloak management for 20M+ users.
Ready to simplify yours?