- Keycloak SSO accepted unverified email claims, and all SSO providers (Keycloak, Entra ID, SimpleSAML) could resolve a claimed email address to an existing account that was created via a different sign-in method, enabling cross-provider account collision and unauthorized access to another user's account and data.
- Entra ID role mapping relied on group display names, which tenant members could duplicate by creating a group with the same name as a privileged group (e.g. FlowintelAdmin), resulting in unauthorized role escalation.
- SSO provisioning reused organisations whose display names matched user-controlled profile names, granting the new SSO user access to that organisation's private cases without explicit administrator assignment.
- Case sharing via the API resolved organisations by name using a first-match query, so ambiguous names could silently resolve to the wrong organisation.
Preconditions: an attacker must have a valid SSO identity (Keycloak, Entra ID, or SimpleSAML) or be a member of the relevant Entra tenant. No local administrator access is required.
Security impact: unauthorized access to private case data, privilege escalation to Editor or higher roles, and account takeover across authentication providers.
Affected versions: Flowintel prior to 4.1.0.
Metrics
Affected Vendors & Products
No advisories yet.
Solution
The fix enforces strict identity and organisation trust boundaries across all SSO providers. Keycloak now requires a verified email claim and no longer falls back to preferred_username. A new shared identity-resolution function rejects any email that maps to an account registered under a different sign-in provider, preventing cross-provider account collision. Entra ID role mapping now requires configured group object IDs (UUIDs) instead of display names, eliminating the name-duplication escalation vector. Default organisation creation always allocates a new organisation rather than reusing one by name match. Case sharing via the API now rejects ambiguous organisation names and requires an explicit organisation ID.
Workaround
No workaround given by the vendor.
Fri, 20 Nov 2026 11:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Flowintel contains multiple SSO identity and organisation trust boundary violations that collectively allow account takeover, privilege escalation, and unauthorized access to private case data. - Keycloak SSO accepted unverified email claims, and all SSO providers (Keycloak, Entra ID, SimpleSAML) could resolve a claimed email address to an existing account that was created via a different sign-in method, enabling cross-provider account collision and unauthorized access to another user's account and data. - Entra ID role mapping relied on group display names, which tenant members could duplicate by creating a group with the same name as a privileged group (e.g. FlowintelAdmin), resulting in unauthorized role escalation. - SSO provisioning reused organisations whose display names matched user-controlled profile names, granting the new SSO user access to that organisation's private cases without explicit administrator assignment. - Case sharing via the API resolved organisations by name using a first-match query, so ambiguous names could silently resolve to the wrong organisation. Preconditions: an attacker must have a valid SSO identity (Keycloak, Entra ID, or SimpleSAML) or be a member of the relevant Entra tenant. No local administrator access is required. Security impact: unauthorized access to private case data, privilege escalation to Editor or higher roles, and account takeover across authentication providers. Affected versions: Flowintel prior to 4.1.0. | |
| Title | Flowintel SSO Identity and Organisation Trust Boundary Violations Allow Account Takeover, Privilege Escalation, and Unauthorized Case Access | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-287 CWE-639 |
|
| CPEs | cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Flowintel
Flowintel flowintel |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: CIRCL
Published:
Updated: 2026-11-20T10:55:52.251Z
Reserved: 2026-11-20T10:55:47.105Z
Link: CVE-2026-133659
No data.
Status : Received
Published: 2026-11-20T11:18:33.880
Modified: 2026-11-20T11:18:33.880
Link: CVE-2026-133659
No data.
OpenCVE Enrichment
No data.