Flowintel contains multiple SSO identity and organisation trust boundary violations that collectively allow account
Source GCVE Database
Not known to be exploited · CVSS 8.6 High : upgrade to 4.1.0 soon.
Data as of 20 Nov 2026, 13:48 UTC
Thin evidence
One scorer or none| CNA (CIRCL) | CVSS 4.0 | 8.6 |
|---|
- Patch
- Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 19 Nov 2026.
What to do
Upgrade flowintel to 4.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| flowintelflowintel | Affected
| Fixed in
|
GitHubflowintelpkg:github/flowintelOther 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
A fix is available in Flowintel version 4.1.0 and later. Users should upgrade to version 4.1.0 or newer to remediate these vulnerabilities. No additional mitigation steps are indicated in the advisory.
Description
Flowintel prior to version 4.1.0 contains multiple security flaws in its Single Sign-On (SSO) implementation that allow attackers with valid SSO identities to take over accounts, escalate privileges, and access private case data without authorization. These issues arise from unverified email claims in Keycloak, ambiguous role mapping in Entra ID, reuse of organization names matching user profile names, and ambiguous organization resolution in API case sharing. Exploitation requires only a valid SSO identity or membership in the relevant Entra tenant, with no local admin access needed.