Quick answers
- Is CVE-2026-81817 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81817 being exploited in the wild.
- How severe is CVE-2026-81817?
- Informational severity, with a CVSS score of 5.4, published 27 August 2026.
- Which products and versions are affected?
- FlowIntel 3.3.0 and prior.
- Is there a fix for CVE-2026-81817?
- A patch was published on 2026-08-18. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-81817 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-81817?
- Check whether you run FlowIntel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a broken object-level authorization (BOLA) flaw affecting numerous task-related endpoints in Flowintel. Endpoints accepted both a case identifier (cid) and task identifier (tid) but did not validate that the task actually belonged to the specified case. An authenticated editor-level user could substitute a task ID from a different case into requests to edit, delete, modify notes, assign, change status, manage files, or perform other operations on that foreign task. The patch introduces a task_case_bound_required decorator that validates task ownership by verifying task.case_id matches the requested case before proceeding, and adds explicit note_id ownership checks. The vulnerability required authentication and editor-level access but no additional user interaction; network reachability to the application was sufficient to exploit it.
Affected products
- Flowintel Flowintel 3.3.0 and prior
Timeline
- 2026-08-27: disclosed
- 2026-08-18: patched