CVE-2026-133662: flowintel Analyzer: Missing Authorization on Result Reads and Case/Task Writes (IDOR)
flowintel contains multiple authorization bypass vulnerabilities in its Analyzer (MISP Modules) functionality, affecting both the web interface and the REST API.
- Saving analyzer results to a case or task accepted caller-supplied case and task identifiers without verifying that the authenticated user is a member of the target case or holds the required restricted-task permissions. An authenticated user could write notes, create tasks, and attach MISP objects or attributes into another organization's case.
- Stored analyzer results were retrievable by UUID by any authenticated user. Both the web endpoint and the API endpoint returned the full result payload without checking ownership, exposing another user's analysis output.
- The save handler did not validate the structure of the request, did not reject conflicting destination selections, and did not halt processing when a task-note operation failed, allowing partial or unintended writes.
Preconditions: the attacker must possess a valid authenticated session (or API token) in flowintel. No administrative role is required.
Security impact: unauthorized cross-tenant data disclosure (analyzer results) and unauthorized cross-tenant data modification (notes, tasks, MISP objects/attributes in another organization's case).
Affected versions: flowintel prior to 4.1.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
flowintelto a version that resolves this vulnerability.Fixed in 4.1.0
Event History
Frequently Asked Questions
Who can exploit these authorization failures?
Any user with a valid authenticated flowintel web session or API token can exploit them. No administrative role is required.
What access does an attacker need to read analyzer results or write to another tenant's case?
The attacker needs to be authenticated and able to supply a stored analyzer-result UUID or target case/task identifiers. The affected handlers did not verify ownership, case membership, or required restricted-task permissions.
What could an attacker do in another organization's workspace?
They could retrieve the full payload of stored analyzer results by UUID. They could also write notes, create tasks, and attach MISP objects or attributes to another organization's case or task.
Are both browser-based and API users affected?
Yes. The unauthorized result retrieval affected both web and REST API endpoints, and the Analyzer save functionality accepted caller-supplied destination identifiers.
What additional behavior could cause unintended changes during exploitation?
The save handler did not validate request structure or reject conflicting destination selections. It also continued processing after a task-note operation failed, which could result in partial or unintended writes.