Keycloak Advisory Watch

Archives
Log in
Subscribe
November 9, 2026

Keycloak security fixes in 26.8.2

Keycloak 26.8.2 shipped on 2026-11-05. Its release notes list 33 security fixes, each with its own CVE, and none of them is on Keycloak's GitHub advisory feed. Keycloak labels one critical, 15 high and 17 medium. No 26.7.x release carries them, so on 26.7 clearing them still means the minor upgrade.

Keycloak CVEs

CVE Severity Summary Issue
CVE-2026-111497 Critical Out-of-bounds write in bundled Brotli decoder #54333
CVE-2026-112208 High Account takeover via stale SSO_AUTH note in Organization identity-first login (reproduced on 26.8.1) #54688
CVE-2026-110932 High Unauthenticated persistent disk exhaustion (theme gzip cache) #54689
CVE-2026-107602 High Unauthenticated CPU and worker-pool exhaustion (restart required) via SAML 1.1 KeyInfo parser loop on a legal ds:KeyName #54692
CVE-2026-110931 High Unauthenticated single-request JVM termination (OutOfMemoryError) via SAML 1.1 AuthorityBinding parser loop, incomplete fix of CVE-2026-7307 #54693
CVE-2026-114232 High UMA user-managed permission resourceType field not validated, cross-owner resource access #54696
CVE-2026-97847 High Client manager can replace a sessionless token principal and take over the realm #54697
CVE-2026-96457 High Group-admin DENY bypass via top-level move (GroupsResource, CVE-2026-9099 regression) #54699
CVE-2026-93998 High SAML adapter accepts assertions from the wrong configured issuer #54703
CVE-2026-96453 High kcadm custom truststores trust arbitrary self-signed certificates #54704
CVE-2026-92857 High Identity spoofing: a default-allowed DCR protocol mapper writes the reserved sub and aud claims #54705
CVE-2026-103112 High Account Takeover via Authentication Race #54706
CVE-2026-97175 High Unverified IdP email auto-linking enables account takeover #54707
CVE-2026-82965 High SAML SOAP endpoint DoS via unbounded XML parsing on /realms/{realm}/protocol/saml/resolve #54709
CVE-2026-92855 High Keycloak SAML Broker Accepts Holder-of-Key Assertions Without Proof of Key Possession #54711
CVE-2026-117691 High SAML redirect binding signature bypass via percent-encoded parameter name (%53AMLResponse), broker login as any user #54714
CVE-2026-92358 Medium Cross-browser fallback proof survives successful account linking and self-service unlink #53061
CVE-2026-105305 Medium Device Authorization Grant bypasses per-client minimum.acr.value enforcement #53618
CVE-2026-107623 Medium OIDC DCR read-modify-write silently disables offline token revocation on backchannel logout #53749
CVE-2026-107889 Medium Stored XSS on the login page via kcSanitize bypass #53813
CVE-2026-112201 Medium Login-failure upsert trusts MySQL/MariaDB affected-row count #54687
CVE-2026-107123 Medium Unauthenticated DoS in Keycloak SAML endpoint #54690
CVE-2026-107124 Medium Session takeover by victim logout with injected id_token_hint #54691
CVE-2026-97367 Medium DCR azp+sid claim substitution via User Property mappers allows Account REST victim session takeover #54694
CVE-2026-97174 Medium CIBA sub parameter injection causes attacker authentication to issue victim tokens #54695
CVE-2026-96547 Medium DCR registration-time claim-path gap: attribute mappers forge realm_access.roles from user-editable fields #54698
CVE-2026-96460 Medium Token from token exchange can have unlimited expiration #54700
CVE-2026-97848 Medium Protocol mapper with jsonType=JSON bypasses CVE-2026-16102 fix, duplicate resource_access claim in access token; forged resource_access in ID token, userinfo and introspection response #54701
CVE-2026-109081 Medium Principal with only create-client can inject a role into the realm default-roles #54702
CVE-2026-96447 Medium Stateless token preferred_username fallback enables identity rebinding after client recreation #54708
CVE-2026-96448 Medium FGAP v2 composite-blind role mapping lets manage-users assign a wrapper containing realm-admin #54710
CVE-2026-92856 Medium Keycloak SAML Identity Broker Ignores ProxyRestriction, Allowing Forbidden Downstream Assertion Issuance #54712
CVE-2026-19688 Medium Admin API missing audience check #54713

Severity is Keycloak's own label on each issue. Eight of the rows are SAML, and three of those are titled unauthenticated. The critical one is the Brotli decoder bundled in the Quarkus distribution.

Three rows reopen fixes from earlier batches: CVE-2026-110931 is an incomplete fix of CVE-2026-7307, CVE-2026-96457 is a regression of CVE-2026-9099, and CVE-2026-97848 bypasses the CVE-2026-16102 fix. If you patched for those and stopped there, you are exposed again.

The notes also list 5 weaknesses with no CVE id. One, #53535, lets an unsigned SAML client log a victim out of another service provider by spoofing its Issuer.

What clears them

  • On 26.8.0 or 26.8.1: 26.8.2 clears everything above.
  • On 26.7.x: there is no 26.7.6, and no row is labelled for 26.7. Clearing them means the minor upgrade to 26.8.2, so read the migration guide first.
  • On 26.6.x: 30 rows are labelled for 26.6.8, and the SAML signature bypass (CVE-2026-117691) for 26.6.9. Both are tagged in the repository, but neither has a GitHub release or an image on quay.io as of 2026-11-06. The MySQL/MariaDB login-failure fix and the group-admin regression are labelled for 26.8.2 only.
  • On 26.4.x: 15 rows are labelled for 26.4.17 and one for 26.4.18. Both are tags only, with no release.

What breaks on the way there

We rehearsed both common jumps in our lab on 2026-11-06: 1,002 users, PostgreSQL 16, the official image. 26.7.3 to 26.8.2 was ready 19 seconds after stop, running 27 changesets. 26.0.0 to 26.8.2 took 23 seconds and 94 changesets. Both ended on migration model 26.8.2 with the index audit at 122 of 122, and a rollback restored each in 20 seconds, losing the write made after the backup.

One thing broke. The fix for CVE-2026-19688 makes the Admin API check the token's audience. A service-account client with view-users got 401 on the Admin API after the upgrade, using the same token as before. It needs the new kc-admin-api client scope, which the upgrade adds only to admin-cli and the admin console. The 26.8.2 upgrading guide documents it, and it applies to anyone already on 26.8.0. Add the scope to your automation clients before the version moves.

Minor hops are also where the Java API moves. Every minor hop we measured removed between 17 and 137 signatures a custom provider could name (api-removals-by-hop, finding 1). If you run custom providers, build them against 26.8.2 before the version moves.


Written by Ben Hart at MLabs. We rehearse Keycloak upgrades against seeded datasets in a lab and publish the records. We also run these upgrades, and the certificate lifecycle around them, for teams who would rather not. Talk to us about your project.

Don't miss what's next. Subscribe to Keycloak Advisory Watch:
Older → Keycloak security fixes in 26.8.1
Powered by Buttondown, the easiest way to start and grow your newsletter.