Skip to main content
Menu
CVEs

flowintel account takeover in SSO login handling

Affects Flowintel before 4.1.0 when it uses Keycloak SSO, Entra ID role mapping, or default organisation creation. Fixed in 4.1.0.

CVE-2026-133659EUVD-2026-131453GHSA-F6MH-J93F-5J88Published , updated

8.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.1.0
Who is exposed
Specific setups only

Summary

Flowintel's single sign-on handling for Keycloak, Entra ID, and SimpleSAML has several trust flaws that let a remote attacker with a valid SSO identity, or membership in the relevant Entra tenant, take over other accounts, gain Editor or higher roles, and read private case data. The attack works over the network without any user action and does not require local administrator access.

Written by a model

Original 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.

What to do

  1. Check whether your setup matches what the bug needs.

    Keycloak SSO accepting unverified email claims or falling back to preferred_username Entra ID role mapping based on group display names Default organisation creation reusing an existing organisation by name match
  2. Upgrade to a fixed version: 4.1.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133659 (Flowintel SSO Identity and Organisation Trust Boundary Violations Allow Account Takeover, Privilege Escalation, and Unauthorized Case Access), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133659 (entry last updated 2026-11-20):
Affected:
- flowintel flowintel: fixed in 4.1.0
Fixed versions: 4.1.0.
Conditions (all must be true for the bug to be hit):
- Keycloak SSO accepting unverified email claims or falling back to preferred_username (source: https://www.cve.org/CVERecord?id=CVE-2026-133659)
- Entra ID role mapping based on group display names (source: https://www.cve.org/CVERecord?id=CVE-2026-133659)
- Default organisation creation reusing an existing organisation by name match (source: https://www.cve.org/CVERecord?id=CVE-2026-133659)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-133659 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133659 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/flowintel/flowintel/commit/a39038de93a46911e0d13283d5fa7812e114538b
- https://www.cve.org/CVERecord?id=CVE-2026-133659
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133659
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133659"}.

Affected versions

cve.now Index

18Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.6/10CVSS 8.6, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133659
RecordNVD · CVE-2026-133659
Other links 1
PatchGitHub · flowintel/flowintel · Commit a39038de

Questions about CVE-2026-133659

Is CVE-2026-133659 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The advisory describes trust boundary violations in Flowintel's SSO and organisation handling, with the outcomes named in its title: account takeover, privilege escalation, and unauthorized case access. Keycloak SSO could accept unverified email claims or fall back to preferred_username, Entra ID role mapping matched group display names, and default organisation creation could reuse an existing organisation by name match.

Source: cve.org

Which versions are affected by CVE-2026-133659?

flowintel: before 4.1.0.

Source: cve.now feed data

Am I affected, and how do I check?

Flowintel versions before 4.1.0 are affected. The exposed setups are Keycloak SSO that accepts unverified email claims or falls back to preferred_username, Entra ID role mapping based on group display names, and default organisation creation that reuses an organisation by name match. To check, compare your installed version with 4.1.0, then review your Keycloak email claim and fallback settings and whether Entra ID role mapping uses group object IDs or display names.

Source: cve.org

How do I fix CVE-2026-133659?

Upgrade to Flowintel 4.1.0 or later. In that version Keycloak requires a verified email claim and no longer falls back to preferred_username, Entra ID role mapping requires configured group object IDs (UUIDs) instead of display names, and default organisation creation always allocates a new organisation.

Source: cve.org

No corrections so far. Something wrong on this page? Report an error.