CVE-2025-1391: Red Hat build of Keycloak 26.0 · Improper Access Control
Affects Red Hat build of Keycloak 26.0Source CVE Database V5
Not known to be exploited · CVSS 5.4 Medium : upgrade to 26.0.10 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 26.0.10
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade keycloak-services to 26.0.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat Build of Keycloak | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.0 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.0 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.0 | Affected– | Fixed in– |
GitHubkeycloak-servicespkg:github/keycloak-servicesOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Red Hat has released fixed versions of Keycloak 26.0.10 that address this vulnerability. Users of affected Keycloak 26.0.0 should update to the latest Red Hat build of Keycloak 26.0.10 images as provided in the Red Hat advisories RHSA-2025:2544 and RHSA-2025:2545. Before updating, back up existing installations including configurations and databases. Patch status is confirmed as fixed by Red Hat. No additional mitigation steps are indicated beyond applying the official update.
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.
References
- access.redhat.com/errata/RHSA-2025:2544 (opens in a new tab)
- access.redhat.com/errata/RHSA-2025:2545 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2025-1391 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2346082 (opens in a new tab)
- github.com/keycloak/keycloak/issues/37169 (opens in a new tab)
- github.com/keycloak/keycloak/pull/37235 (opens in a new tab)