This meant that a user who was a connector owner of an alert could continue to read alert details, review history, raw payloads, and action comments, and could perform review-status updates or case-creation actions, even after their access to the linked private case had been revoked or they were never a member of that case.
Additionally, a time-of-check to time-of-use (TOCTOU) gap existed: after a review-status update or a competing case-creation claim was committed, the response could disclose private case identifiers or review history to a user whose access had been concurrently removed by another session linking the alert to a private case.
Impact:
- Unauthorized disclosure of private case data (review comments, raw payloads, action history) through alert endpoints.
- Unauthorized modification of alert review status and creation of cases from alerts the user should no longer access.
- Leakage of a competing case identifier to an unauthorized user during concurrent case-creation races.
Affected versions: FlowIntel prior to 4.1.0.
No advisories yet.
Solution
The fix enforces private case visibility as a mandatory gate before any connector-ownership check can grant alert access. If an alert is linked to a private case and the user cannot view that case, access is denied regardless of ownership. A post-commit re-verification is added after review-status updates and after detecting a competing case-creation claim, ensuring that concurrent association changes do not result in unauthorized data disclosure in the response.
Workaround
No workaround given by the vendor.
Fri, 20 Nov 2026 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FlowIntel's alerting module contained an authorization bypass in the alert access control logic. When an alert was linked to a private case, the system relied solely on connector ownership (user or organization) to determine access, without verifying that the requesting user still held valid membership in the associated private case. This meant that a user who was a connector owner of an alert could continue to read alert details, review history, raw payloads, and action comments, and could perform review-status updates or case-creation actions, even after their access to the linked private case had been revoked or they were never a member of that case. Additionally, a time-of-check to time-of-use (TOCTOU) gap existed: after a review-status update or a competing case-creation claim was committed, the response could disclose private case identifiers or review history to a user whose access had been concurrently removed by another session linking the alert to a private case. Impact: - Unauthorized disclosure of private case data (review comments, raw payloads, action history) through alert endpoints. - Unauthorized modification of alert review status and creation of cases from alerts the user should no longer access. - Leakage of a competing case identifier to an unauthorized user during concurrent case-creation races. Affected versions: FlowIntel prior to 4.1.0. | |
| Title | FlowIntel Alerting: Missing Private Case Authorization Check Allows Connector Owners to Access Revoked Case Data | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-362 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-20T16:34:09.703Z
Reserved: 2026-11-20T14:40:00.274Z
Link: CVE-2026-133851
No data.
Status : Received
Published: 2026-11-20T15:17:53.533
Modified: 2026-11-20T17:18:23.083
Link: CVE-2026-133851
No data.
OpenCVE Enrichment
No data.