Description
flowintel is a case management application that enforces an approval workflow for tasks in privileged cases. Tasks in such cases are required to start in a Requested status, meaning they must receive explicit approval before becoming active.

A logic flaw in the task-creation path allowed tasks to be initialized with a Created status (bypassing the approval step) in two scenarios:

- When a task was created from a template and no acting user was supplied, the privileged-case check was skipped entirely, leaving the task in Created status.
- When a case was created from a template, all copied tasks were unconditionally assigned the Created status regardless of the case's privileged designation.

An authenticated user with the ability to create tasks from templates or to instantiate cases from templates could therefore place tasks directly into an active state within privileged cases, circumventing the intended approval gate. This may expose restricted case content or permit actions that should require supervisory sign-off.

Affected versions: flowintel prior to 4.1.0.
Published: 2026-11-20
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

Vendor Solution

The approval-workflow enforcement for privileged cases is now applied unconditionally at task creation time. The privileged-case check no longer depends on the presence of an acting user, and template-based case creation explicitly assigns the configured Requested status to tasks when the target case is privileged. Ordinary (non-privileged) cases retain the default Created status, preserving existing behavior.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 20 Nov 2026 14:45:00 +0000

Type Values Removed Values Added
Description flowintel is a case management application that enforces an approval workflow for tasks in privileged cases. Tasks in such cases are required to start in a Requested status, meaning they must receive explicit approval before becoming active. A logic flaw in the task-creation path allowed tasks to be initialized with a Created status (bypassing the approval step) in two scenarios: - When a task was created from a template and no acting user was supplied, the privileged-case check was skipped entirely, leaving the task in Created status. - When a case was created from a template, all copied tasks were unconditionally assigned the Created status regardless of the case's privileged designation. An authenticated user with the ability to create tasks from templates or to instantiate cases from templates could therefore place tasks directly into an active state within privileged cases, circumventing the intended approval gate. This may expose restricted case content or permit actions that should require supervisory sign-off. Affected versions: flowintel prior to 4.1.0.
Title flowintel Privileged Case Task Approval Bypass via Missing User Context and Template Creation
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

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Flowintel Flowintel
cve-icon MITRE

Status: PUBLISHED

Assigner: CIRCL

Published:

Updated: 2026-11-20T14:40:25.523Z

Reserved: 2026-11-20T14:40:19.091Z

Link: CVE-2026-133852

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-20T15:17:53.743

Modified: 2026-11-20T15:17:53.743

Link: CVE-2026-133852

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses