CVE-2026-133659
Flowintel SSO Identity and Organisation Trust Boundary Violations Allow Account Takeover, Privilege Escalation, and Unauthorized Case Access
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.
INFO
Published Date :
Nov. 20, 2026, 10:55 a.m.
Last Modified :
Nov. 20, 2026, 10:55 a.m.
Remotely Exploit :
Yes !
Source :
CIRCL
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 4.0 | HIGH | 5a6e4751-2f3f-4070-9419-94fb35b644e8 |
Solution
- Validate SSO identity claims and prevent cross-provider account collision.
- Enforce secure role mapping based on unique identifiers.
- Implement strict organization matching during SSO provisioning.
- Refine API organization resolution to prevent ambiguous name matches.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-133659 vulnerability anywhere in the article.