CVE-2026-18215Keycloak provides a way to let users log in using Microsoft accounts while restricting access to a specific organization (tenant).
Updated under an hour ago ()
Does this affect you?
It affects redhat build_of_keycloak. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 8.1 HIGH (v3.1, NVD)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Weakness (CWE)
- CWE-287
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Modified
- Record last updated
- Sep 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
redhat build_of_keycloak redhat:build_of_keycloak | all versions | NVD |
References
- https://access.redhat.com/errata/RHSA-2026:68277
- https://access.redhat.com/errata/RHSA-2026:68278
- https://access.redhat.com/security/cve/CVE-2026-18215vendor-advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2508309issue-tracking, vendor-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.