CVE-2026-81817
Last modified
CVE-2026-81817 is a high-severity vulnerability rated 7.2/10 on the CVSS scale. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
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
Metrics
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| flowintel | flowintel | <= 3.3.0 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-81817?
How severe is CVE-2026-81817?
How do I fix CVE-2026-81817?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-8178An issue exists in Amazon Redshift JDBC Driver versions prio…9.2
- CVE-2026-81780Unauthenticated Arbitrary File Upload in Hash Form <= 1.4.2 …10
- CVE-2026-8179IBM Aspera High-Speed Transfer Endpoint 3.7.4 through 4.4.7 …8.8
- CVE-2026-8180IBM Aspera High-Speed Transfer Endpoint 3.7.4 through 4.4.7 …7.5
- CVE-2026-8181The Burst Statistics – Privacy-Friendly WordPress Analytics …9.8
- CVE-2026-81814Affected versions of Flowintel render calendar event titles …5.1
- CVE-2026-81818Affected versions of Flowintel contain an authorization flaw…8.6
- CVE-2026-81819Affected versions of Flowintel expose the /my_assignment/use…5.3
- CVE-2026-8182IBM Langflow OSS 1.0.0 through 1.10.3 installations allow an…8.8
- CVE-2026-81820Affected versions of Flowintel construct timeline HTML using…5.1
- CVE-2026-81826Affected versions of Flowintel do not revoke existing authen…9.1
- CVE-2026-81827Affected versions of Flowintel incorrectly attempted to vali…6.9
Are you affected by CVE-2026-81817?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
