- Connector instance metadata, connectivity checks, and case listings accepted instance IDs without verifying if the acting user had visibility or ownership rights, allowing unauthorized access to sensitive configuration and data.
- Case template serialization and creation processes exposed connector instances attached to templates regardless of the user's permissions, potentially leaking credentials or instance details to users who should not have access.
- Editing connector instances allowed changes to URLs or sharing scopes without requiring re-authentication of API keys, enabling the reuse of another user's credentials in a new context or the leakage of shared keys to unauthorized endpoints.
- Outbound MISP connector keys were incorrectly accepted for authenticating incoming alerts, bypassing the intended separation between outbound integration credentials and inbound alert source authentication.
These issues allow authenticated users to access unauthorized connector data, manipulate credential scopes, and potentially exploit credential confusion between different security contexts.
Affected versions: < 4.1.0
No advisories yet.
Solution
The patch enforces strict visibility and ownership checks on all connector instance access paths, including metadata retrieval, connectivity tests, and case listings. It ensures that case templates only expose and copy connector instances visible to the acting user. Additionally, it mandates API key re-entry when changing instance URLs or sharing scopes to prevent credential leakage or unauthorized reuse. Finally, it decouples outbound MISP keys from incoming alert authentication, requiring distinct credentials for alert ingestion.
Workaround
No workaround given by the vendor.
Fri, 20 Nov 2026 11:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FlowIntel contains multiple authorization and credential management vulnerabilities affecting connector instances, MISP helper tools, and case templates. - Connector instance metadata, connectivity checks, and case listings accepted instance IDs without verifying if the acting user had visibility or ownership rights, allowing unauthorized access to sensitive configuration and data. - Case template serialization and creation processes exposed connector instances attached to templates regardless of the user's permissions, potentially leaking credentials or instance details to users who should not have access. - Editing connector instances allowed changes to URLs or sharing scopes without requiring re-authentication of API keys, enabling the reuse of another user's credentials in a new context or the leakage of shared keys to unauthorized endpoints. - Outbound MISP connector keys were incorrectly accepted for authenticating incoming alerts, bypassing the intended separation between outbound integration credentials and inbound alert source authentication. These issues allow authenticated users to access unauthorized connector data, manipulate credential scopes, and potentially exploit credential confusion between different security contexts. Affected versions: < 4.1.0 | |
| Title | FlowIntel: Missing Authorization and Credential Scope Enforcement in Connector and Template Features | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-287 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-20T10:57:13.587Z
Reserved: 2026-11-20T10:57:10.196Z
Link: CVE-2026-133661
No data.
Status : Received
Published: 2026-11-20T11:18:34.303
Modified: 2026-11-20T11:18:34.303
Link: CVE-2026-133661
No data.
OpenCVE Enrichment
No data.