Skip to main content
VulnerabilityPublished

CVE-2026-133659: flowintel · Improper Authentication

Affects flowintelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 4.1.0 soon.

Data as of 20 Nov 2026, 11:19 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (CIRCL)CVSS 4.08.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
flowintelflowintelAffected
  • <4.1.0
Fixed in
  • 4.1.0
GitHubflowintelpkg:github/flowintelOther threatsAffected
  • <4.1.0
Fixed in
  • 4.1.0

CPE configurations (1)

  • cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Flowintel to version 4.1.0 or later, where these authentication and authorization issues have been fixed. No additional mitigations are specified by the vendor advisory. Applying the official fix fully addresses the vulnerabilities.

Description

Flowintel versions prior to 4.1.0 contain multiple improper authentication vulnerabilities involving SSO identity and organization trust boundaries. These flaws allow attackers with a valid SSO identity or membership in the relevant Entra tenant to perform account takeover, privilege escalation, and unauthorized access to private case data. Key issues include acceptance of unverified email claims by Keycloak SSO, cross-provider account collision, role mapping based on duplicable group display names in Entra ID, reuse of organizations by matching display names, and ambiguous organization resolution in case sharing APIs. The vulnerabilities are fixed in version 4.1.0.

References

Community reviews

Loading reviews…