Preconditions:
- An authenticated user with access to the chatbot interface.
- Concurrent or overlapping chatbot tool invocations from different users, or a request made after another user's credentials were written to the process environment.
Impact:
- A lower-privilege user could read data belonging to a higher-privilege user (e.g., private investigation cases).
- A user whose session was invalidated (deleted, password changed, key revoked) could still operate under a previously cached ambient credential.
- The parent process environment was mutated with user-specific secrets, creating a persistent credential leak surface.
Affected versions: FlowIntel prior to 4.1.0.
Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
The shared persistent MCP session and process-wide API key mutation were removed. Each chatbot tool invocation now spawns its own short-lived MCP child process with credentials resolved fresh from the authenticated request context. If the user's identity or API key is unavailable, the invocation is rejected before any child process is launched, preventing fallback to ambient or stale credentials. Each transport is deterministically closed on success, failure, or timeout, eliminating residual credential exposure.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 20 Nov 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FlowIntel's chatbot component used a single shared MCP (Model Context Protocol) session and process-wide environment variable to pass per-user API credentials to a child process. Because the session and the ambient FLOWINTEL_API_KEY environment variable were shared across all concurrent requests, a user's authenticated identity could be applied to another user's tool invocation, or a stale/ambient credential could be inherited by a new request. Preconditions: - An authenticated user with access to the chatbot interface. - Concurrent or overlapping chatbot tool invocations from different users, or a request made after another user's credentials were written to the process environment. Impact: - A lower-privilege user could read data belonging to a higher-privilege user (e.g., private investigation cases). - A user whose session was invalidated (deleted, password changed, key revoked) could still operate under a previously cached ambient credential. - The parent process environment was mutated with user-specific secrets, creating a persistent credential leak surface. Affected versions: FlowIntel prior to 4.1.0. | |
| Title | FlowIntel Chatbot Shared MCP Session Allows Cross-User API Identity Confusion | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-200 CWE-290 |
|
| CPEs | cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Flowintel
Flowintel flowintel |
|
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: CIRCL
Published:
Updated: 2026-11-20T14:44:31.341Z
Reserved: 2026-11-20T14:44:25.304Z
Link: CVE-2026-133853
No data.
Status : Received
Published: 2026-11-20T15:17:53.947
Modified: 2026-11-20T15:17:53.947
Link: CVE-2026-133853
No data.
OpenCVE Enrichment
No data.