{"api_version":"1","generated_at":"2026-11-20T19:06:13+00:00","cve":"CVE-2026-133659","urls":{"html":"https://cve.report/CVE-2026-133659","api":"https://cve.report/api/cve/CVE-2026-133659.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-133659","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-133659"},"summary":{"title":"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.\n\n- 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.\n\n- 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.\n\n- 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.\n\n- Case sharing via the API resolved organisations by name using a first-match query, so ambiguous names could silently resolve to the wrong organisation.\n\nPreconditions: 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.\n\nSecurity impact: unauthorized access to private case data, privilege escalation to Editor or higher roles, and account takeover across authentication providers.\n\nAffected versions: Flowintel prior to 4.1.0.","state":"PUBLISHED","assigner":"CIRCL","published_at":"2026-11-20 11:18:33","updated_at":"2026-11-20 17:18:20"},"problem_types":["CWE-287","CWE-639","CWE-287 CWE-287 Improper Authentication","CWE-639 CWE-639 Authorization Bypass Through User-Controlled Key"],"metrics":[{"version":"4.0","source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","type":"Secondary","score":"8.6","severity":"HIGH","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","data":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","baseScore":8.6,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}},{"version":"4.0","source":"CNA","type":"CVSS","score":"8.6","severity":"HIGH","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","data":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"NETWORK","baseScore":8.6,"baseSeverity":"HIGH","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnerabilityResponseEffort":"NOT_DEFINED"}}],"references":[{"url":"https://github.com/flowintel/flowintel/commit/a39038de93a46911e0d13283d5fa7812e114538b","name":"https://github.com/flowintel/flowintel/commit/a39038de93a46911e0d13283d5fa7812e114538b","refsource":"5a6e4751-2f3f-4070-9419-94fb35b644e8","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-133659","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-133659","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"flowintel","product":"flowintel","version":"affected 4.1.0 semver","platforms":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"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.","time":"","lang":"en"}],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"elhoim","lang":"en"},{"source":"CNA","value":"David Cruciani","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-133659","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"role":"CISA Coordinator","timestamp":"2026-11-20T16:24:17.180170Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-11-20T16:38:40.476Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"cpes":["cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"],"modules":["app/account/keycloak_core.py","app/account/entra_core.py","app/account/simplesaml_core.py","app/account/sso_identity.py","app/admin/admin_core.py","app/case/case_api.py","app/case/common_core.py"],"product":"flowintel","programFiles":[],"repo":"https://github.com/flowintel/flowintel","vendor":"flowintel","versions":[{"lessThan":"4.1.0","status":"affected","version":"0","versionType":"semver"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*","vulnerable":true}],"negate":false,"operator":"OR"}]}],"credits":[{"lang":"en","type":"reporter","value":"elhoim"},{"lang":"en","type":"remediation developer","value":"David Cruciani"}],"descriptions":[{"lang":"en","value":"Flowintel contains multiple SSO identity and organisation trust boundary violations that collectively allow account takeover, privilege escalation, and unauthorized access to private case data.\n\n- 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.\n\n- 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.\n\n- 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.\n\n- Case sharing via the API resolved organisations by name using a first-match query, so ambiguous names could silently resolve to the wrong organisation.\n\nPreconditions: 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.\n\nSecurity impact: unauthorized access to private case data, privilege escalation to Editor or higher roles, and account takeover across authentication providers.\n\nAffected versions: Flowintel prior to 4.1.0."}],"impacts":[{"capecId":"CAPEC-126","descriptions":[{"lang":"en","value":"CAPEC-126 Exploiting Incorrectly Handled Edge Cases"}]}],"metrics":[{"cvssV4_0":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"NETWORK","baseScore":8.6,"baseSeverity":"HIGH","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnerabilityResponseEffort":"NOT_DEFINED"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]},{"format":"SSVC","other":{"content":{"options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"total"}],"role":"Supplier","timestamp":"2026-11-20T10:46:18Z","version":"2.0.3"},"type":"SSVC"},"scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-287","description":"CWE-287 Improper Authentication","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-639","description":"CWE-639 Authorization Bypass Through User-Controlled Key","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-20T10:55:52.251Z","orgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","shortName":"CIRCL"},"references":[{"name":"Security patch","tags":["patch"],"url":"https://github.com/flowintel/flowintel/commit/a39038de93a46911e0d13283d5fa7812e114538b"}],"solutions":[{"lang":"en","value":"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."}],"title":"Flowintel SSO Identity and Organisation Trust Boundary Violations Allow Account Takeover, Privilege Escalation, and Unauthorized Case Access","x_gcve":[{"extensions":{"bcp-05-x-01":{"ai_annotations":[{"ai_level":"generated","description":"Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.","gna_source":1,"models":[{"gna_source":1,"identifier":"qwen3.8:27b","name":"qwen3.8:27b","source":"ollama"}],"review_status":"full","scope":"record","tags":["ai-computer-assisted:llm-generated","ai-computer-assisted:classification"]}]},"bcp-05-x-02":{"x_patch2vuln":{"assumptions":["The affected version range is assumed to be all versions prior to 4.1.0 based on the explicit context; the patch does not contain version-specific markers.","PR:L assumes the attacker already possesses a valid SSO identity or Entra tenant membership; the patch does not specify whether SSO is enabled by default.","CAPEC-126 is selected as the closest available attack pattern; no CAPEC specifically covers identity-confusion or name-collision attacks, so this mapping is approximate.","The CVSS vector assumes the SSO endpoints are reachable over the network without additional network segmentation; the patch does not specify deployment topology.","The patch does not indicate whether the vulnerabilities were disclosed under a coordinated disclosure program or whether a CVE has been assigned."],"capecRationale":[{"capecId":"CAPEC-126","rationale":"The vulnerabilities arise from the application incorrectly handling edge cases in identity resolution: unverified email claims, cross-provider email collisions, duplicate group display names, and duplicate organisation names. The application assumed these identifiers were unique and trustworthy when they were not. CAPEC-126 is the closest available pattern; a more specific CAPEC for identity-confusion or name-collision attacks does not exist in the CAPEC catalogue, making this the best available match."}],"commit":"a39038de93a46911e0d13283d5fa7812e114538b","confidence":"high","credits":[{"lang":"en","type":"reporter","value":"elhoim"},{"lang":"en","type":"remediation developer","value":"David Cruciani"}],"cvssRationale":"AV:N: SSO endpoints are network-accessible. AC:L: the attack requires only a valid SSO identity or tenant membership; no race conditions or special timing. AT:N: no manipulation of a separate attack target is needed. PR:L: the attacker needs a low-privilege SSO account or tenant membership. UI:N: no victim interaction is required; the collision occurs server-side during provisioning or login. VC:H: unauthorized access to private case data and account information. VI:H: privilege escalation via group name duplication and account takeover via cross-provider email collision. VA:N: no denial-of-service impact. SC:N: all impacts are confined to the Flowintel application. SI:N: no impact on other components. SA:N: no safety impact.","fixSummary":"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.","generatedAt":"2026-11-20T10:46:18.874266Z","generator":"patch2vuln.py","model":"qwen3.8:27b","modelComparison":{"potentialErrors":[],"rankings":[{"agreementScore":11,"assumptionCount":5,"confidence":"high","model":"qwen3.8:27b","score":8}],"selectedModel":"qwen3.8:27b","selectionMethod":"deterministic-consensus-v1","selectionNotice":"The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."},"patchSha256":"af2c034661f80ca4205759cb6ed41f0aca0adb9867e4538c7c4847835cff6b74","patchSummary":"Added app/account/sso_identity.py with a find_sso_user() helper that resolves an email only within its existing auth_provider and returns an error on cross-provider collision. Keycloak token validation now requires email_verified to be true and removes the preferred_username fallback. Entra group resolution switched from displayName to object ID (UUID) with regex validation; default group names removed from config. create_default_org() in admin_core.py now always creates a new Org instead of querying by name. get_org_by_name() in common_core.py changed from .first() to .one_or_none() to raise MultipleResultsFound on ambiguity. case_api.py catches MultipleResultsFound and returns a 400 error directing the caller to use oid. Configuration defaults, template.env, and installation documentation updated to reflect UUID-based group configuration and new SSO identity rules.","patchTruncated":false,"patches":[{"commit":"a39038de93a46911e0d13283d5fa7812e114538b","date":"Mon, 2 Nov 2026 10:44:03 +0100","patchSha256":"af2c034661f80ca4205759cb6ed41f0aca0adb9867e4538c7c4847835cff6b74","retrievedAt":"2026-11-20T10:45:41.638629Z","source":"https://github.com/flowintel/flowintel/commit/a39038de93a46911e0d13283d5fa7812e114538b.patch","sourceUrl":"https://github.com/flowintel/flowintel/commit/a39038de93a46911e0d13283d5fa7812e114538b.patch","subject":"fix: [security] SSO identities and organisations respect"}],"source":"https://github.com/flowintel/flowintel/commit/a39038de93a46911e0d13283d5fa7812e114538b.patch","ssvc":{"options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"total"}],"role":"Supplier","timestamp":"2026-11-20T10:46:18Z","version":"2.0.3"},"subject":"fix: [security] SSO identities and organisations respect","weaknessRationale":[{"cweId":"CWE-287","rationale":"Keycloak accepted unverified email claims and all SSO providers resolved emails to accounts regardless of the original sign-in method, allowing an attacker to authenticate as a different user's identity. This is a failure to properly validate the identity assertion during authentication."},{"cweId":"CWE-639","rationale":"Entra ID role mapping used user-controllable group display names as the authorization key, and organisation provisioning used user-controlled profile names as the lookup key. An attacker could duplicate these names to gain unauthorized roles or organisation membership."}]}},"bcp-05-x-03":{"x_timeline":{"events":[{"description":"Corrective change authored (a39038de93a46911e0d13283d5fa7812e114538b): fix: [security] SSO identities and organisations respect","id":"evt-fix-developed-1","references":["https://github.com/flowintel/flowintel/commit/a39038de93a46911e0d13283d5fa7812e114538b.patch"],"timestamp":"2026-11-02T09:44:03Z","type":"fix-developed"},{"description":"Patch retrieved from the supplied URL; retrieval time is used as the default availability time.","id":"evt-fix-available-1","references":["https://github.com/flowintel/flowintel/commit/a39038de93a46911e0d13283d5fa7812e114538b.patch"],"timestamp":"2026-11-20T10:45:41.638629Z","type":"fix-available"}]}}},"recordType":"advisory","vulnId":"GCVE-1-2026-20400"}]}},"cveMetadata":{"assignerOrgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","assignerShortName":"CIRCL","cveId":"CVE-2026-133659","datePublished":"2026-11-20T10:55:52.251Z","dateReserved":"2026-11-20T10:55:47.105Z","dateUpdated":"2026-11-20T16:38:40.476Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 11:18:33","lastModifiedDate":"2026-11-20 17:18:20","problem_types":["CWE-287","CWE-639","CWE-287 CWE-287 Improper Authentication","CWE-639 CWE-639 Authorization Bypass Through User-Controlled Key"],"metrics":{"cvssMetricV40":[{"source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","type":"Secondary","cvssData":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","baseScore":8.6,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}}],"ssvcV203":[{"source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","ssvcData":{"timestamp":"2026-11-20T10:46:18Z","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"role":"Supplier","version":"2.0.3"}},{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-11-20T16:24:17.180170Z","id":"CVE-2026-133659","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"133659","Ordinal":"1","Title":"Flowintel SSO Identity and Organisation Trust Boundary Violation","CVE":"CVE-2026-133659","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"133659","Ordinal":"1","NoteData":"Flowintel contains multiple SSO identity and organisation trust boundary violations that collectively allow account takeover, privilege escalation, and unauthorized access to private case data.\n\n- 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.\n\n- 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.\n\n- 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.\n\n- Case sharing via the API resolved organisations by name using a first-match query, so ambiguous names could silently resolve to the wrong organisation.\n\nPreconditions: 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.\n\nSecurity impact: unauthorized access to private case data, privilege escalation to Editor or higher roles, and account takeover across authentication providers.\n\nAffected versions: Flowintel prior to 4.1.0.","Type":"Description","Title":"Flowintel SSO Identity and Organisation Trust Boundary Violation"}]}}}