CVE-2026-81817

published 27 Aug 2026 · updated 27 Aug 2026

Flowintel Missing Task-to-Case Authorization Allows Cross-Case Task Modification

7.2HighCVSS 7.2EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
flowintel<=3.3.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-81817 severity on Zeptric[![CVE-2026-81817](https://zeptric.io/badge/cve/CVE-2026-81817.svg)](https://zeptric.io/cve/CVE-2026-81817)