Security readout for executives and security teams
Plain-English summary
CVE-2025-1391 can cause Keycloak tokens to claim a user belongs to an organization when they do not. The mismatch happens when a username or email matches an organization domain pattern. Business risk depends on whether downstream applications trust those organization claims for access decisions.
Executive priority
Treat this as a targeted identity authorization risk, not a broad system compromise. Prioritize environments where Keycloak organization claims grant customer, tenant, or administrative access.
Technical view
The flaw is an improper authorization issue in the Keycloak organization mapper. It may assign organization claims based on username or email domain pattern matching rather than actual membership, causing token misrepresentation. CVSS is 5.4 with low attack complexity, required user privileges, no user interaction, and limited confidentiality and integrity impact.
Likely exposure
Exposure is most likely in Red Hat Build of Keycloak 26.0 or keycloak-services 26.0 deployments using the organization feature, especially where applications authorize access based on organization claims in tokens.
Exploitation context
The source bundle does not show known active exploitation, and KEV is false. Exploitation would require an authenticated user and an environment where organization claims influence authorization decisions.
Researcher notes
Key details needing confirmation from vendor material include exact fixed versions and mapper behavior after remediation. Focus analysis on token claim generation, organization membership checks, and downstream authorization dependence.
Mitigation direction
- Apply Red Hat guidance from RHSA-2025:2544 and RHSA-2025:2545 where applicable.
- Inventory Keycloak 26.0 and Red Hat Build of Keycloak 26.0 deployments.
- Review organization mapper configurations and domain pattern rules.
- Ensure applications do not trust organization claims without membership verification.
- Check vendor advisories for fixed builds and upgrade instructions.
Validation and detection
- Confirm whether the organization feature is enabled in affected deployments.
- Identify applications that authorize users based on organization token claims.
- Compare installed packages against the affected versions in the source bundle.
- Verify tokens only include organizations backed by explicit membership.
- Review access logs for organization-based privileges granted to non-members.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-1391 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5redhatVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Made public.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2025:2544CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2025:2545CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2025-1391CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2346082CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/keycloak/keycloak/issues/37169CVE reference, redhat
- https://github.com/keycloak/keycloak/pull/37235CVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.