Description
A flaw was found in the Keycloak organization feature, which allows the incorrect assignment of an organization to a user if their username or email matches the organization’s domain pattern. This issue occurs at the mapper level, leading to misrepresentation in tokens. If an application relies on these claims for authorization, it may incorrectly assume a user belongs to an organization they are not a member of, potentially granting unauthorized access or privileges.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
keycloak-services
Default version status: unaffected
26.0.0 to < 26.0.10affected
Red Hat Red Hat Build of Keycloak
Default version status: unaffected
Red Hat Red Hat build of Keycloak 26.0
Default version status: affected
26.0.10-3 to < *unaffected
Red Hat Red Hat build of Keycloak 26.0
Default version status: affected
26.0-11 to < *unaffected
Red Hat Red Hat build of Keycloak 26.0
Default version status: affected
26.0-12 to < *unaffected
References
- https://access.redhat.com/errata/RHSA-2025:2544 ↗
- https://access.redhat.com/errata/RHSA-2025:2545 ↗
- https://access.redhat.com/security/cve/CVE-2025-1391 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=2346082 ↗
- https://github.com/keycloak/keycloak/issues/37169 ↗
- https://github.com/keycloak/keycloak/pull/37235 ↗