CVE-2026-133658: flowintel · Improper Authorization
Affects flowintelSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.1.0 when convenient.
Data as of 20 Nov 2026, 11:19 UTC
Thin evidence
One scorer or none| CNA (CIRCL) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/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 vulnerability is fixed. No other mitigations are specified or required once the official fix is applied.
Description
Flowintel versions prior to 4.1.0 contain a privilege escalation vulnerability in the Matrix relay integration. The vulnerability arises from a mismatch in authorization checks where the relay bot's elevated permissions were used to evaluate API requests, but the request handlers enforced the represented user's lower privileges. This allowed users with restricted roles, such as Read Only, to perform unauthorized write operations and modifications. Additionally, the relay's authority was determined by editable user profile fields, enabling impersonation of the trusted relay bot by ordinary users who altered their profile name and email. The issue is fixed in version 4.1.0.