# CVE-2026-81817: Flowintel Missing Task-to-Case Authorization Allows Cross-Case Task Modification

> Authenticated users can modify tasks belonging to other cases by manipulating task identifiers, bypassing object-level authorization checks.

- **Severity:** High 7.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-ccgv-2jpf-98m2

## What is CVE-2026-81817?

CVE-2026-81817 is a high-severity missing authorization vulnerability in flowintel, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-81817?


## How do I fix CVE-2026-81817?

No fix has been published for CVE-2026-81817 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-81817 being exploited?

There is no known exploitation of CVE-2026-81817 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81817 and fix it if it is affected.

What it is: CVE-2026-81817 is a high-severity missing authorization vulnerability in flowintel, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81817 in the wild and no public exploit code.

Affected product: flowintel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81817/ (Markdown: https://insights.sbomify.com/CVE-2026-81817/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81817
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81817
- OSV: https://osv.dev/vulnerability/CVE-2026-81817

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81817/
Summaries are generated and may contain mistakes; the official description above is the record.