CVE-2026-18215 Keycloak-services: keycloak-services: microsoft external access-token exchange bypasses configured tenant

Medium 6.8 Published Updated

Attackers can bypass tenant restrictions in Microsoft token exchange to access unauthorized Keycloak realms and sensitive data.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-18215?

CVE-2026-18215 is a medium-severity authentication bypass vulnerability in Redhat Build of Keycloak, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Keycloak provides a way to let users log in using Microsoft accounts while restricting access to a specific organization (tenant). A flaw was discovered where this restriction is ignored when using the token exchange feature. This means an attacker with a valid Microsoft token from a completely different organization could gain access to the Keycloak realm, potentially accessing sensitive data or performing unauthorized actions.

Weakness: CWE-287

Which versions are affected by CVE-2026-18215?

1 open source package ship an affected version, including keycloak. It affects 1 product.

PackageAffectedFixed in
keycloak BitnamiAll versions26.7.3

Products include Redhat Build of Keycloak.

How do I fix CVE-2026-18215?

Upgrade keycloak to 26.7.3 or later.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-18215 being exploited?

There is no known exploitation of CVE-2026-18215 in the wild and no public exploit code.

All Redhat Build of Keycloak vulnerabilities

Sources

Also known as BIT-keycloak-2026-18215, CLEANSTART-2026-HB26759, GHSA-v8h5-7wp9-qxxv.

Is CVE-2026-18215 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free