Affected operations include:
- Self-unassignment from a restricted task
- Reordering tasks, including indirectly moving restricted sibling tasks
- Linking or unlinking MISP objects and attributes to/from restricted tasks
- Creating MISP objects or standalone attributes with task IDs referencing restricted tasks
- Deleting MISP objects or attributes that are linked to restricted tasks
- Executing modules on restricted tasks
A user with case member access (but without Admin, Case Admin, or Queue Admin privileges) could exploit these paths to alter the state of tasks that are supposed to be locked pending approval, effectively bypassing the intended approval workflow and potentially manipulating associated MISP data.
Affected versions: FlowIntel prior to 4.1.0
Metrics
Affected Vendors & Products
No advisories yet.
Solution
The fix enforces approver-level permission checks (is_task_restricted and can_edit_requested_task) before any state change on restricted tasks across all affected code paths. Checks are applied at both the model layer (TaskCore, CaseCore) and the API/view layer (case_api, case_misp, task), rejecting forbidden operations with a 403 response before any partial writes occur. Reordering additionally validates every affected restricted sibling task, and module execution requires approver permission before dispatch.
Workaround
No workaround given by the vendor.
Fri, 20 Nov 2026 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FlowIntel contains an authorization bypass that allows non-approver case members to modify restricted tasks (those in Requested, Rejected, or Request Review status) through several indirect code paths that lacked the required approver permission check. Affected operations include: - Self-unassignment from a restricted task - Reordering tasks, including indirectly moving restricted sibling tasks - Linking or unlinking MISP objects and attributes to/from restricted tasks - Creating MISP objects or standalone attributes with task IDs referencing restricted tasks - Deleting MISP objects or attributes that are linked to restricted tasks - Executing modules on restricted tasks A user with case member access (but without Admin, Case Admin, or Queue Admin privileges) could exploit these paths to alter the state of tasks that are supposed to be locked pending approval, effectively bypassing the intended approval workflow and potentially manipulating associated MISP data. Affected versions: FlowIntel prior to 4.1.0 | |
| Title | FlowIntel Missing Authorization on Restricted Task Modification Paths | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-862 | |
| CPEs | cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Flowintel
Flowintel flowintel |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: CIRCL
Published:
Updated: 2026-11-20T14:36:06.945Z
Reserved: 2026-11-20T14:35:59.942Z
Link: CVE-2026-133838
No data.
No data.
No data.
OpenCVE Enrichment
No data.