flowintel versions prior to 4.1.0 contain an information disclosure vulnerability in the case history feature. Authenticated users authorized to view a case's history may see references to other cases they are not permitted to access, exposing identifiers and titles of sensitive investigations. This occurs across multiple output methods including browser view, API, and report downloads. The issue arises from the presentation layer failing to filter unauthorized case references, bypassing intended per-case access controls. The vulnerability is fixed in version 4.1.0.
flowintel versions prior to 4.1.0 contain a missing authorization vulnerability in the case and task classification usage endpoints. Authenticated users can access classification data for cases they are not authorized to view because object-level access controls are not properly enforced. This exposure includes taxonomies, tags, galaxies, clusters, and custom tags associated with private or restricted cases. The vulnerability could disclose sensitive information about case existence and threat classifications, aiding reconnaissance or targeting efforts.
CVE-2026-133853 is an authentication bypass vulnerability in FlowIntel's chatbot component prior to version 4.1.0. The flaw arises because the system uses a single shared MCP session and a process-wide environment variable to pass per-user API credentials, causing credentials to be shared across concurrent requests. This can lead to unauthorized access where a lower-privilege user may access data belonging to a higher-privilege user, and invalidated sessions may still operate under stale credentials.
flowintel versions prior to 4.1.0 contain a logic flaw in task creation that allows bypassing the required approval workflow for privileged cases. Specifically, tasks can be initialized directly in an active Created status instead of the intended Requested status under two conditions involving templates. This flaw enables authenticated users with task or case creation permissions to circumvent supervisory approval, potentially exposing restricted content or unauthorized actions.
FlowIntel versions prior to 4.1.0 contain an authorization bypass vulnerability in the alert access control logic. Users who are connector owners of alerts linked to private cases could access and modify alert details even after losing membership in those cases. A time-of-check to time-of-use (TOCTOU) race condition could also expose private case identifiers to unauthorized users during concurrent case-creation attempts. This vulnerability allows unauthorized disclosure and modification of sensitive alert and case data.
flowintel versions prior to 4.1.0 contain an authorization flaw in the recurring reminder notification subsystem. Users who had access to private cases but later lost that access can still receive and view recurring reminder notifications related to those cases. This flaw allows unauthorized information disclosure of case titles, reminder messages, and metadata without affecting data integrity or availability. The issue is fixed in version 4.1.0.
CVE-2026-133849 is a high-severity authorization bypass vulnerability in flowintel's calendar functionality prior to version 4.1.0. The flaw allowed users to view tasks in calendar views without proper verification of their permission to access the parent case, potentially exposing private case data. The issue was fixed in flowintel 4.1.0 by enforcing case visibility checks alongside task assignment and organization membership.
flowintel versions prior to 4.1.0 have an authorization vulnerability in the user deletion functionality. Organization-scoped administrators can delete platform-level administrator accounts within their organization due to improper enforcement of privilege hierarchy. This flaw allows lower-privilege org admins to remove higher-privilege platform admins, leading to loss of administrative oversight and potential disruption of platform management. The issue is fixed in version 4.1.0.
flowintel versions prior to 4.1.0 contain an authorization bypass vulnerability in the browser-based admin user editing interface. Organization-admin users could modify platform-admin accounts due to missing authorization checks, potentially altering credentials, roles, or other attributes. This flaw allows unauthorized modification of platform-admin accounts, risking privilege escalation and administrative lockout. The issue was fixed in version 4.1.0.
FlowIntel versions prior to 4.1.0 contain an authorization bypass vulnerability in the task management workflow. This flaw allows users with basic task-level permissions to revive completed privileged cases by reopening tasks or creating new tasks within those cases. The system does not enforce required Admin or Case Admin privilege checks before reviving cases, leading to unauthorized case lifecycle changes and potential exposure to further unauthorized modifications.
FlowIntel versions prior to 4.1.0 have an information disclosure vulnerability in their case serialization logic. Authenticated users with read access to a case could see connector metadata belonging to other users or organizations, including URLs, descriptions, UUIDs, and possibly API credentials. This exposure crosses organizational boundaries and reveals sensitive connector infrastructure details.
flowintel versions prior to 4.1.0 contain an authorization bypass vulnerability in the MISP correlation feature. The system does not properly verify user permissions when generating correlation lists for MISP attributes, allowing authenticated users to discover case identifiers they should not access. This leads to unauthorized information disclosure of case existence.
FlowIntel versions prior to 4.1.0 contain an authorization bypass vulnerability in the case serialization logic. Authenticated users with access to any case linked to private cases can view metadata such as identifiers, titles, and descriptions of those private cases without proper authorization. This issue affects multiple access paths including browser views, REST API endpoints, and internal tooling. The vulnerability arises because the serialization method does not verify the requesting user's permissions before including linked-case data in responses.
flowintel versions prior to 4.1.0 contain an authorization bypass vulnerability in the file-to-note conversion feature for case tasks in restricted workflow states. Authenticated users with basic case membership roles such as editor or queuer can perform conversion actions on tasks in restricted states (Requested, Rejected, or Request Review) without requiring elevated roles. This allows unauthorized reading of attached file contents and creation of notes on restricted tasks, bypassing intended workflow restrictions.
FlowIntel versions prior to 4.1.0 contain a missing authorization vulnerability in the task file deletion functionality. Authenticated users with low-privilege case membership roles (such as editor or queuer) could delete evidence files associated with tasks in restricted states, an action that should have been limited to Admin-level roles. This flaw affects the core deletion logic, browser interface, and REST API endpoints, allowing unauthorized deletion of files, timeline events, and history logs. The vulnerability compromises the integrity of investigations by enabling destruction of evidence and alteration of case history. The issue is fixed in version 4.1.0.
FlowIntel versions prior to 4.1.0 contain an authorization bypass vulnerability (CWE-862) that allows non-approver case members to modify tasks that should be restricted and pending approval. This includes operations such as self-unassignment, reordering tasks, linking/unlinking MISP objects, creating or deleting MISP objects or attributes related to restricted tasks, and executing modules on these tasks. The flaw enables users with limited privileges to circumvent the approval workflow and alter task states and associated data.
flowintel versions prior to 4.1.0 contain an authorization bypass vulnerability in the task completion workflow for privileged cases. Users with lower-privilege roles such as editor or queuer could mark tasks as completed without the required approver review from higher-privilege roles. This bypass undermines the mandatory approval process and allows unauthorized modification of task completion states.
flowintel versions prior to 4.1.0 contain multiple DOM-based cross-site scripting (XSS) vulnerabilities. Authenticated attackers able to create or import specially crafted case content can inject arbitrary HTML or script into pages viewed by other users. The flaws arise from improper sanitization in timeline rendering, search highlighting, and content-type handling endpoints. Successful exploitation can lead to script execution in victims' browsers, potentially exposing case data or allowing actions under the victim's identity. The issue is fixed in version 4.1.0.
flowintel versions prior to 4.1.0 have an information disclosure vulnerability that allows authenticated non-administrative users to access sensitive configuration data and logs intended only for administrators. Sensitive fields such as webhook URLs, signing secrets, IMAP credentials, and delivery logs are exposed in notification pages and alert API responses. Although the UI hides these configurations from non-admin users, the underlying data remains accessible via page source or API endpoints. This exposure includes historical webhook URLs that may contain active bearer tokens. An attacker with a valid non-admin account could exploit this to gain unauthorized access to notification services, impersonate the application, or move laterally within the infrastructure. The vulnerability is fixed in version 4.1.0.
flowintel versions prior to 4.1.0 contain an authorization bypass vulnerability (CVE-2026-133663) due to insecure direct object references (IDOR) in multiple endpoints managing child records of cases and tasks. Authenticated users can access or modify data belonging to other cases by supplying identifiers of those records without proper ownership verification. This affects reading, editing, and deleting of task notes, subtasks, timeline events, connectors, and connector operations across unauthorized cases. The vulnerability allows exfiltration of sensitive threat intelligence and unauthorized modification or deletion of data, impacting data integrity and incident response workflows.