Description
Affected versions of Flowintel contain an insecure direct object reference / broken object-level authorization issue across numerous task endpoints.


The routes generally received both a case identifier and a task identifier, but previously they did not enforce that the task actually belonged to the supplied case. As a result, an authenticated user with editor-level access to one case could potentially substitute the ID of a task from another case and invoke operations against that foreign task.


The patch introduces task_case_bound_required, which loads both objects and returns 404 unless the task belongs to the requested case. This protection is applied to edit, delete, note, assignment, status, file, export, MISP-linking, subtask, external-reference, and other task-related endpoints.

The fix also adds explicit checks that a requested note_id belongs to the current task before returning or exporting it, closing related cross-object access paths.

Version impacted =>3.3.0
Published: 2026-08-27
Score: 7.2 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Flowintel versions prior to the security update contain a broken object‑level authorization flaw (CWE‑639). The flaw allows an authenticated user with editor‑level access to one case to use the task ID of a task from another case to modify, delete, or otherwise manipulate the foreign task. This can result in unauthorized changes to task data, loss of integrity, and potential disruption of case management workflows.

Affected Systems

The vulnerability affects Flowintel (flowintel:flowintel) in versions 3.3.0 and later. Users deploying these versions should inspect whether they are running the patched code that enforces the task‑to‑case relationship.

Risk and Exploitability

The CVSS score of 7.2 indicates a high‑severity impact. Since the user can authenticate and has editor level rights, the attacker does not need elevated privileges or system access. Although EPSS is not available and the vulnerability is not listed in CISA’s KEV catalog, the exposed endpoint allows relatively straightforward exploitation by an authorized user with cross‑case access rights.

Generated by OpenCVE AI on August 27, 2026 at 18:34 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the official patch from Flowintel's GitHub repository or upgrade to the latest stable release that includes the task_case_bound_required protection.
  • Restart or reload the Flowintel service to ensure the updated code is active.
  • Review and, if necessary, restrict editor‑level permissions so that users can only edit tasks belonging to cases they own; consider removing cross‑case editing rights in temporary configuration if immediate patching is not possible.

Generated by OpenCVE AI on August 27, 2026 at 18:34 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 27 Aug 2026 18:00:00 +0000

Type Values Removed Values Added
First Time appeared Flowintel
Flowintel flowintel
Vendors & Products Flowintel
Flowintel flowintel

Thu, 27 Aug 2026 16:45:00 +0000

Type Values Removed Values Added
Description Affected versions of Flowintel contain an insecure direct object reference / broken object-level authorization issue across numerous task endpoints. The routes generally received both a case identifier and a task identifier, but previously they did not enforce that the task actually belonged to the supplied case. As a result, an authenticated user with editor-level access to one case could potentially substitute the ID of a task from another case and invoke operations against that foreign task. The patch introduces task_case_bound_required, which loads both objects and returns 404 unless the task belongs to the requested case. This protection is applied to edit, delete, note, assignment, status, file, export, MISP-linking, subtask, external-reference, and other task-related endpoints. The fix also adds explicit checks that a requested note_id belongs to the current task before returning or exporting it, closing related cross-object access paths. Version impacted =>3.3.0
Title Flowintel Missing Task-to-Case Authorization Allows Cross-Case Task Modification
Weaknesses CWE-639
References
Metrics cvssV4_0

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


Subscriptions

Flowintel Flowintel
cve-icon MITRE

Status: PUBLISHED

Assigner: CIRCL

Published:

Updated: 2026-08-27T19:44:14.187Z

Reserved: 2026-08-27T13:10:27.900Z

Link: CVE-2026-81817

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-27T17:21:05.207

Modified: 2026-08-27T20:18:55.793

Link: CVE-2026-81817

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-27T19:00:06Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key