A user with basic task-level permissions (e.g., editor, queuer, or queue admin) could trigger the revival of a completed privileged case through the browser interface or the REST API, without holding the elevated role required for case-level operations. This could disrupt case lifecycle management, clear completion metadata, and potentially expose the case to further unauthorized modifications.
The vulnerability affects both the browser-based task completion/status-change endpoints and the corresponding API endpoints, as well as the task creation flow.
Affected versions: FlowIntel prior to 4.1.0.
Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
The fix introduces explicit authorization checks (can_reopen_case and can_reopen_task) that require Admin or Case Admin privileges before a completed privileged case can be revived as a side effect of task reopening or task creation. Denial is enforced at the core model layer and at both the browser and API endpoint layers, with audit logging of denied attempts. Legitimate task creation is preserved, but the automatic case revival is suppressed for unauthorized users.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 20 Nov 2026 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FlowIntel contains an authorization bypass in its task management workflow. When a user reopens a completed task (by toggling its completion state or changing its status to a non-finished value) or creates a new task within a completed privileged case, the parent case is automatically revived (un-completed, status reset to Created, finish date cleared). The system failed to enforce the required Admin or Case Admin privilege check before performing this case revival side effect. A user with basic task-level permissions (e.g., editor, queuer, or queue admin) could trigger the revival of a completed privileged case through the browser interface or the REST API, without holding the elevated role required for case-level operations. This could disrupt case lifecycle management, clear completion metadata, and potentially expose the case to further unauthorized modifications. The vulnerability affects both the browser-based task completion/status-change endpoints and the corresponding API endpoints, as well as the task creation flow. Affected versions: FlowIntel prior to 4.1.0. | |
| Title | FlowIntel Missing Authorization Check Allows Unauthorized Revival of Completed Privileged Cases via Task Reopening | |
| 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
|
Status: PUBLISHED
Assigner: CIRCL
Published:
Updated: 2026-11-20T16:35:10.072Z
Reserved: 2026-11-20T14:38:25.137Z
Link: CVE-2026-133846
No data.
Status : Received
Published: 2026-11-20T15:17:52.540
Modified: 2026-11-20T17:18:22.280
Link: CVE-2026-133846
No data.
OpenCVE Enrichment
No data.