When a case is linked to another case, the JSON representation of the source case included the ID, title, and description of every linked case regardless of the requesting user's permissions. This affected multiple access paths:
- Browser views (case detail, case info, search, calendar)
- REST API endpoints (get case, list cases, search, title lookup, completed/not-completed lists)
- Internal tooling and connector module context building
An attacker with valid credentials and access to any case that contains a link to a private case could enumerate the private case's identifier, title, and description without holding a membership or role on that private case. The exposure occurred because the serialization method did not receive or evaluate the acting user's identity before including linked-case data in the response.
Security impact:
- Disclosure of private case identifiers, titles, and descriptions to unauthorized users
- Facilitation of further targeted attacks against the exposed private cases
- Bypass of the intended per-case access control model
Affected versions: FlowIntel prior to 4.1.0
No advisories yet.
Solution
The serialization method now accepts the acting user as a parameter and filters linked cases based on the user's authorization. When an authenticated user is provided, only linked cases the user is permitted to view are included. When no user is provided (internal or anonymous callers), the method fails closed by excluding all private linked cases. All call sites across browser views, API endpoints, calendar, search, tools, and internal core operations were updated to pass the resolved user identity, ensuring consistent enforcement regardless of the access path.
Workaround
No workaround given by the vendor.
Fri, 20 Nov 2026 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FlowIntel contains an authorization bypass in its case serialization logic that allows an authenticated user to view metadata of private cases they do not have access to. When a case is linked to another case, the JSON representation of the source case included the ID, title, and description of every linked case regardless of the requesting user's permissions. This affected multiple access paths: - Browser views (case detail, case info, search, calendar) - REST API endpoints (get case, list cases, search, title lookup, completed/not-completed lists) - Internal tooling and connector module context building An attacker with valid credentials and access to any case that contains a link to a private case could enumerate the private case's identifier, title, and description without holding a membership or role on that private case. The exposure occurred because the serialization method did not receive or evaluate the acting user's identity before including linked-case data in the response. Security impact: - Disclosure of private case identifiers, titles, and descriptions to unauthorized users - Facilitation of further targeted attacks against the exposed private cases - Bypass of the intended per-case access control model Affected versions: FlowIntel prior to 4.1.0 | |
| Title | FlowIntel Information Disclosure of Linked Private Case Metadata via Unfiltered Case Serialization | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-200 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-20T14:37:27.260Z
Reserved: 2026-11-20T14:37:21.756Z
Link: CVE-2026-133841
No data.
No data.
No data.
OpenCVE Enrichment
No data.