CVE-2026-133847: flowintel · Missing Authorization
Affects flowintelSource CVE Database V5
Not known to be exploited · CVSS 8.4 High : upgrade to 4.1.0 soon.
Data as of 20 Nov 2026, 14:51 UTC
Thin evidence
One scorer or none| CNA (CIRCL) | CVSS 4.0 | 8.4 |
|---|
- Patch
- Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/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
|
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 this authorization bypass vulnerability has been fixed. No other mitigation is required as the fix addresses the inconsistent authorization checks in the browser-based admin interface.
Description
flowintel versions prior to 4.1.0 contain an authorization bypass vulnerability in the browser-based admin user editing interface. Organization-admin users could modify platform-admin accounts due to missing authorization checks, potentially altering credentials, roles, or other attributes. This flaw allows unauthorized modification of platform-admin accounts, risking privilege escalation and administrative lockout. The issue was fixed in version 4.1.0.