- Note variable references (e.g. cross-case or cross-task lookups) were resolved using the viewing user's privileges rather than the destination case's audience. An authenticated user with access to a shared or imported note could embed references to private cases, causing sensitive case data to be pulled into AI report requests, exports, and MISP sends without the referenced case's audience having granted read access.
- The chatbot API tool permitted the language model to invoke any FlowIntel API endpoint, including administrative routes and state-changing GET operations, without an allow-list or path validation. An attacker who can influence the model's instructions (e.g. via untrusted case content) could induce data modification or access restricted endpoints.
- AI report generation passed the Ollama bearer token and full case content as command-line arguments to a child process, exposing them in the system process table to any local user.
Affected versions: FlowIntel prior to 4.1.0.
No advisories yet.
Solution
Three remediations are applied: (1) Note variable resolution now enforces an audience-based authorization check so that cross-case and cross-task references only expand when the destination case's assigned organisations can read the referenced case; (2) the chatbot API tool is restricted to an explicit allow-list of reviewed read-only and search operations, with administrative endpoints always blocked, path validation against injection and SSRF, and write operations gated behind an explicit CHATBOT_ALLOW_WRITES configuration flag; (3) AI report requests are delivered to the child process via a private anonymous temporary file on stdin instead of argv, keeping credentials and case content out of the process listing.
Workaround
No workaround given by the vendor.
Fri, 20 Nov 2026 09:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FlowIntel contains multiple security flaws in its note variable resolution, chatbot API tooling, and AI report generation. - Note variable references (e.g. cross-case or cross-task lookups) were resolved using the viewing user's privileges rather than the destination case's audience. An authenticated user with access to a shared or imported note could embed references to private cases, causing sensitive case data to be pulled into AI report requests, exports, and MISP sends without the referenced case's audience having granted read access. - The chatbot API tool permitted the language model to invoke any FlowIntel API endpoint, including administrative routes and state-changing GET operations, without an allow-list or path validation. An attacker who can influence the model's instructions (e.g. via untrusted case content) could induce data modification or access restricted endpoints. - AI report generation passed the Ollama bearer token and full case content as command-line arguments to a child process, exposing them in the system process table to any local user. Affected versions: FlowIntel prior to 4.1.0. | |
| Title | FlowIntel Insecure Note Variable Resolution, Over-Permissive Chatbot API Access, and Credential Exposure in Process Arguments | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-200 CWE-284 CWE-862 |
|
| CPEs | cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Flowintel
Flowintel flowintel |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: CIRCL
Published:
Updated: 2026-11-20T09:11:43.154Z
Reserved: 2026-11-20T09:10:21.313Z
Link: CVE-2026-133631
No data.
Status : Received
Published: 2026-11-20T10:17:11.027
Modified: 2026-11-20T10:17:11.027
Link: CVE-2026-133631
No data.
OpenCVE Enrichment
No data.