First published: Mon Feb 17 2025(Updated: )
# Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-gvgg-2r3r-53x7. This link is maintained to preserve external references. # Original 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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Keycloak | ||
maven/org.keycloak:keycloak-services | <26.1.2 | 26.1.2 |
maven/org.keycloak:keycloak-services | <26.0.10 | 26.0.10 |
maven/org.keycloak:keycloak-services | >=26.1.0<26.1.3 | 26.1.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-1391 is classified as a medium severity vulnerability due to its potential impact on user organization assignments in Keycloak.
To fix CVE-2025-1391, update Red Hat Keycloak to the latest version that addresses this vulnerability.
CVE-2025-1391 can lead to improper organization assignments, which may result in incorrect access control and user permissions.
CVE-2025-1391 affects the Red Hat Build of Keycloak, specifically versions prior to the fix.
The root cause of CVE-2025-1391 is a flaw at the mapper level in Keycloak that allows incorrect organization assignment based on matching username or email patterns.