As a result, a user who previously had access to a private case and later had that access revoked can still:
- Receive recurring reminder notifications containing case-related content.
- View stored reminder notifications in their notification list, including notification counts, even though they no longer have permission to view the underlying case.
The vulnerability affects both the notification creation path (recurring reminder generation) and the notification display path (listing and counting stored reminders). The issue arises because the authorization check performed at subscription time is not re-applied at delivery or retrieval time.
Security impact is limited to information disclosure: an unauthorized user may observe case titles, reminder messages, and associated metadata that they no longer have permission to access. No integrity or availability impact is indicated by the patch.
Affected versions: flowintel prior to 4.1.0.
No advisories yet.
Solution
The fix introduces an authorization re-check at two points: (1) before creating a recurring reminder notification, the system now verifies the recipient's current case visibility and skips delivery if access has been revoked; (2) when listing or counting stored notifications, the system now filters out case-related reminder notifications for which the viewing user no longer has case access. This ensures that both the creation and display paths enforce current authorization state rather than relying on a one-time check at subscription time.
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 flaw in its recurring reminder notification subsystem. When a user is subscribed to recurring notifications for a case, the system does not re-verify the recipient's current access rights to that case before generating or displaying the notification. As a result, a user who previously had access to a private case and later had that access revoked can still: - Receive recurring reminder notifications containing case-related content. - View stored reminder notifications in their notification list, including notification counts, even though they no longer have permission to view the underlying case. The vulnerability affects both the notification creation path (recurring reminder generation) and the notification display path (listing and counting stored reminders). The issue arises because the authorization check performed at subscription time is not re-applied at delivery or retrieval time. Security impact is limited to information disclosure: an unauthorized user may observe case titles, reminder messages, and associated metadata that they no longer have permission to access. No integrity or availability impact is indicated by the patch. Affected versions: flowintel prior to 4.1.0. | |
| Title | flowintel: Stale Authorization Allows Notification Disclosure After Case Access Revocation | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-285 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:39:48.936Z
Reserved: 2026-11-20T14:39:45.487Z
Link: CVE-2026-133850
No data.
No data.
No data.
OpenCVE Enrichment
No data.