This means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.
Security impact:
- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.
- Stale access persists indefinitely until the alert is independently re-scoped or deleted.
Affected version: <4.1.0.
Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
The fix ensures that on every duplicate alert update, the ownership and visibility scope fields are unconditionally refreshed from the current connector scope, regardless of the alert's review status. This prevents alerts from retaining a stale, potentially broader visibility scope after the connector's scope has been narrowed or reassigned.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 19 Nov 2026 10:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector's current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector's scope was narrowed or changed. This means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts. Security impact: - Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope. - Stale access persists indefinitely until the alert is independently re-scoped or deleted. Affected version: <4.1.0. | |
| Title | FlowIntel Alert Visibility Scope Not Refreshed on Duplicate Ingestion | |
| First Time appeared |
Flowintel
Flowintel flowintel |
|
| Weaknesses | CWE-668 CWE-862 |
|
| CPEs | cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Flowintel
Flowintel flowintel |
|
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: CIRCL
Published:
Updated: 2026-11-19T10:35:06.740Z
Reserved: 2026-11-19T10:34:56.100Z
Link: CVE-2026-133001
No data.
Status : Received
Published: 2026-11-19T11:17:08.210
Modified: 2026-11-19T11:17:08.210
Link: CVE-2026-133001
No data.
OpenCVE Enrichment
No data.