flowintel versions prior to 4.1.0 contain multiple authorization bypass vulnerabilities in the Analyzer (MISP Modules) functionality affecting both the web interface and REST API. Authenticated users without administrative privileges can write notes, create tasks, and attach MISP objects or attributes to cases belonging to other organizations. Additionally, stored analyzer results can be retrieved by any authenticated user without ownership verification, exposing sensitive analysis data across tenants. The save handler also lacks proper validation, allowing partial or unintended writes. These issues allow unauthorized cross-tenant data disclosure and modification.
FlowIntel versions prior to 4.1.0 contain multiple authorization and credential management vulnerabilities. These flaws allow authenticated users to access connector instance metadata, case listings, and templates without proper permission checks, potentially exposing sensitive configuration and credentials. Additionally, editing connector instances can reuse API keys without re-authentication, and outbound MISP connector keys can be misused for inbound alert authentication, leading to credential confusion. These issues collectively enable unauthorized data access and credential misuse.
FlowIntel versions prior to 4.1.0 contain an authorization bypass vulnerability in user directory and assignment API endpoints. Authenticated users could access user profiles and task assignments from other organizations despite restrictions intended to limit visibility. This includes exposure of user identities, roles, and private case details across organizational boundaries. The issue is fixed in version 4.1.0.
Flowintel versions prior to 4.1.0 contain multiple improper authentication vulnerabilities involving SSO identity and organization trust boundaries. These flaws allow attackers with a valid SSO identity or membership in the relevant Entra tenant to perform account takeover, privilege escalation, and unauthorized access to private case data. Key issues include acceptance of unverified email claims by Keycloak SSO, cross-provider account collision, role mapping based on duplicable group display names in Entra ID, reuse of organizations by matching display names, and ambiguous organization resolution in case sharing APIs. The vulnerabilities are fixed in version 4.1.0.
Flowintel versions prior to 4.1.0 contain a privilege escalation vulnerability in the Matrix relay integration. The vulnerability arises from a mismatch in authorization checks where the relay bot's elevated permissions were used to evaluate API requests, but the request handlers enforced the represented user's lower privileges. This allowed users with restricted roles, such as Read Only, to perform unauthorized write operations and modifications. Additionally, the relay's authority was determined by editable user profile fields, enabling impersonation of the trusted relay bot by ordinary users who altered their profile name and email. The issue is fixed in version 4.1.0.
Flowintel versions prior to 4.1.0 contain a session management vulnerability where session identifiers are numeric user IDs rather than credential-bound tokens. This flaw allows remembered login cookies to remain valid after password changes, enables session fixation due to lack of session rotation on login, and permits attackers with active sessions to change account credentials without verifying the current password. Administrator password resets do not revoke existing sessions or remembered logins, allowing continued unauthorized access. These issues collectively enable attackers who obtain valid sessions or cookies to maintain persistent unauthorized access and take over accounts.
FlowIntel versions prior to 4.1.0 contain a Cross-Site Request Forgery (CSRF) vulnerability affecting fourteen web routes that perform destructive or state-changing operations. These routes accept HTTP GET requests, bypassing CSRF token validation which is only enforced on non-GET requests. An attacker can trick an authenticated user with editor or admin roles into triggering actions such as deletion or modification of cases, tasks, templates, connectors, icons, custom tags, taxonomies, and galaxies without the user's consent. This results in unauthorized data modification and loss of data integrity. The vulnerability is fixed in version 4.1.0.
Flowintel versions prior to 4.1.0 improperly disabled TLS certificate verification for MISP API connections and used unverified SSL contexts for IMAP and SMTP STARTTLS mail connections. This vulnerability allowed a man-in-the-middle attacker to impersonate remote servers, intercept sensitive data including API keys and mail credentials, and modify threat intelligence data exchanged. Exploitation required no authentication and no user interaction, only network positioning between Flowintel and its MISP or mail servers. The issue is fixed in Flowintel 4.1.0.
FlowIntel versions prior to 4.1.0 contain multiple security vulnerabilities related to missing authorization checks, improper API endpoint access controls, and exposure of sensitive tokens. These flaws allow authenticated users to access private case data beyond their privileges, enable the chatbot API to invoke any API endpoint without restrictions, and expose sensitive tokens in system process tables to local users. The issues are fixed in version 4.1.0.
CVE-2026-133630 is a vulnerability in flowintel versions prior to 4.1.0 where the GitHub Actions checkout action used in the Docker build workflow persisted the job authentication token in the repository's Git configuration file. This file was included in the Docker build context and could be retained in exported build cache layers, potentially exposing the token. An attacker with access to the CI/CD build cache or environment could extract this token and gain unauthorized read access to the private source repository.
flowintel versions prior to 4.1.0 contain a log injection vulnerability in the case history audit log subsystem. Authenticated users with case-management access can inject line separator characters into user-controllable fields, causing forged additional log entries attributed to arbitrary users. This compromises the integrity of audit trails by corrupting case history records. The vulnerability affects case history append and merge operations and does not require privilege escalation beyond normal access.
FlowIntel versions prior to 4.1.0 contain a resource exhaustion vulnerability in the file-to-note conversion feature. This flaw occurs when converting CSV or JSON files with a large number of columns or nested JSON keys, causing the application to allocate excessive memory and CPU by padding table cells quadratically. The vulnerability can lead to denial of service by exhausting worker processes, disrupting service availability. No confidentiality or integrity impacts are reported. A fix is available in version 4.1.0.
Flowintel versions prior to 4.1.0 contain a path traversal vulnerability in the template repository subsystem. Authenticated users with permission to add or edit template repositories can exploit insufficient path validation to read arbitrary files on the host system. This occurs because repository registration accepts arbitrary local paths without verifying they reside within the configured base directory, and file lookups use a bypassable path normalization method vulnerable to symbolic link attacks. The vulnerability allows unauthorized reading of sensitive files accessible to the service account.
Flowintel versions up to 4.0.0 have a vulnerability where the admin API key is exposed to any local user during execution of the community data launcher script. The key is passed as a command-line argument to a helper process, which on Unix-like systems can be viewed by other local users via process listing tools. This exposure allows an attacker with local access to gain full administrative control over the Flowintel REST API.
flowintel allows users with editor-level access to author case and task fields, including aggregated tags. When these records are exported as CSV, the field values are written verbatim into the output file.
Because no sanitisation is applied to user-supplied text before CSV serialisation, an attacker can store values that begin with spreadsheet formula triggers (such as =, +, -, @, or their fullwidth Unicode equivalents, or leading control/whitespace characters). When a victim opens the exported CSV in a spreadsheet application (e.g. Microsoft Excel, LibreOffice Calc), the stored text is interpreted and executed as a live formula rather than displayed as literal text.
This can lead to unintended data manipulation within the spreadsheet, potential data exfiltration via formula functions, or execution of downstream commands depending on the spreadsheet application and its configuration.
The vulnerability requires the victim to actively open the CSV file in a spreadsheet application; the flowintel application itself is not directly compromised.
Affected: <4.1.0
flowintel contains a CSV injection vulnerability in its audit log CSV export functionality. Attacker-influenced text recorded in audit logs could be interpreted as spreadsheet formulas when an administrator opened the exported CSV file in a spreadsheet application.
The vulnerable behavior allowed an attacker who could influence audit log content (for example by generating network traffic that is captured and logged) to embed formula-like strings (such as =CMD() or =HYPERLINK()) into audit entries. When the resulting CSV export was opened in a spreadsheet application, these strings could be executed as formulas, potentially leading to data exfiltration, data manipulation, or execution of further malicious actions within the spreadsheet context.
Preconditions:
- An attacker must be able to influence content that is recorded in flowintel audit logs.
- An administrator or user must export the audit logs to CSV and open the file in a spreadsheet application that interprets formulas.
Security impact:
- Potential information disclosure from the spreadsheet or linked resources.
- Potential integrity impact on data within the spreadsheet application.
- No direct compromise of the flowintel application itself.
Affected version: <4.1.0
FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector's current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector's scope was narrowed or changed.
This means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.
Security impact:
- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.
- Stale access persists indefinitely until the alert is independently re-scoped or deleted.
Affected version: <4.1.0.
CVE-2026-124850 is a SQL injection vulnerability in a database migration script of flowintel versions up to 4.0.0. The migration process interpolates stored connector identifier values directly into SQL statements without parameterization, allowing an attacker with prior write access to the database to execute arbitrary SQL during an upgrade. This can lead to unauthorized data disclosure, modification, or deletion.
CVE-2026-0000 is a SQL injection vulnerability in a database migration script of flowintel versions prior to 4.0.0. The migration process interpolates stored connector identifier values directly into SQL statements without parameterization, allowing an attacker with prior write access to the database to execute arbitrary SQL during an upgrade. This can lead to unauthorized data disclosure, modification, or deletion.