{"id":"CVE-2026-133001","state":"PUBLISHED","title":"FlowIntel Alert Visibility Scope Not Refreshed on Duplicate Ingestion","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.\n\nThis 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.\n\nSecurity impact:\n- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.\n- Stale access persists indefinitely until the alert is independently re-scoped or deleted.\n\nAffected version: <4.1.0.","publishedAt":"2026-11-19T10:35:06.740Z","updatedAt":"2026-11-19T17:16:23.842Z","severity":{"score":5.3,"label":"Medium","version":"4.0","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","source":"CIRCL"},"assigner":"CIRCL","products":["flowintel flowintel"],"affected":[{"vendor":"flowintel","product":"flowintel","versions":[{"version":"0","status":"affected","lessThanOrEqual":"4.0.0","versionType":"semver"}],"cpes":["cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"],"modules":["app/alerting/alerting_core.py"],"programFiles":["app/alerting/alerting_core.py"],"repo":"https://github.com/flowintel/flowintel"}],"references":["https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362"],"weaknesses":["CWE-668","CWE-862"],"ingestedAt":"2026-11-19T17:22:06.478Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/133xxx/CVE-2026-133001.json","commit":"e20101a315a22cf309d2aabcfdc6ec38e1eaaab8","baselineCommit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-133001","state":"PUBLISHED","datePublished":"2026-11-19T10:35:06.740Z","dateUpdated":"2026-11-19T17:16:23.842Z","assignerShortName":"CIRCL","assignerOrgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","dateReserved":"2026-11-19T10:34:56.100Z"},"containers":{"cna":{"title":"FlowIntel Alert Visibility Scope Not Refreshed on Duplicate Ingestion","descriptions":[{"lang":"en","value":"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.\n\nThis 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.\n\nSecurity impact:\n- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.\n- Stale access persists indefinitely until the alert is independently re-scoped or deleted.\n\nAffected version: <4.1.0."}],"affected":[{"vendor":"flowintel","product":"flowintel","versions":[{"version":"0","status":"affected","lessThanOrEqual":"4.0.0","versionType":"semver"}],"cpes":["cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"],"modules":["app/alerting/alerting_core.py"],"programFiles":["app/alerting/alerting_core.py"],"repo":"https://github.com/flowintel/flowintel"}],"references":[{"url":"https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362","name":"Security patch","tags":["patch"]}],"metrics":[{"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}],"cvssV4_0":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","baseScore":5.3,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"NONE","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}},{"format":"SSVC","scenarios":[{"lang":"en","value":"GENERAL"}],"other":{"type":"SSVC","content":{"version":"2.0.3","role":"Supplier","timestamp":"2026-11-18T14:20:42Z","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}]}}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-668","lang":"en","description":"CWE-668 Exposure of Resource to Wrong Sphere","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-862","lang":"en","description":"CWE-862 Missing Authorization","type":"CWE"}]}],"providerMetadata":{"shortName":"CIRCL","orgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","dateUpdated":"2026-11-19T10:35:06.740Z"},"solutions":[{"lang":"en","value":"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."}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"}]}]}],"credits":[{"lang":"en","value":"elhoim","type":"reporter"},{"lang":"en","value":"David Cruciani","type":"remediation developer"}],"impacts":[{"capecId":"CAPEC-10","descriptions":[{"lang":"en","value":"CAPEC-10 Leveraging Trusted Relationships"}]}],"x_gcve":[{"vulnId":"gcve-1-2026-20317","recordType":"advisory","extensions":{"bcp-05-x-01":{"ai_annotations":[{"scope":"record","gna_source":1,"tags":["ai-computer-assisted:llm-generated","ai-computer-assisted:classification"],"description":"Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.","ai_level":"generated","review_status":"full","models":[{"name":"qwen3.8:27b","gna_source":1,"source":"ollama","identifier":"qwen3.8:27b"}]}]},"bcp-05-x-02":{"x_patch2vuln":{"generator":"patch2vuln.py","generatedAt":"2026-11-18T14:20:42.931868Z","model":"qwen3.8:27b","source":"https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch","patchSha256":"408047b5b5e090f3bcc7d9a38dcd75dc8fcb0c3d982c82e1bc8a28e6c0f28f8d","patchTruncated":false,"commit":"c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362","subject":"fix: [security] Refresh alert ownership scope on duplicate","patches":[{"source":"https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch","sourceUrl":"https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch","patchSha256":"408047b5b5e090f3bcc7d9a38dcd75dc8fcb0c3d982c82e1bc8a28e6c0f28f8d","commit":"c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362","subject":"fix: [security] Refresh alert ownership scope on duplicate","date":"Fri, 6 Nov 2026 10:54:31 +0100","retrievedAt":"2026-11-18T14:20:07.629180Z"}],"confidence":"medium","assumptions":["The affected version range is not precisely specified in the patch metadata; the affected_version field contains '0' which is treated as a placeholder. All versions prior to commit c158e1bd are assumed affected.","The CAPEC-10 mapping is the closest available match but the vulnerability is more accurately described as a stale-state authorization defect rather than an active exploitation of trust relationships.","The severity of the confidentiality impact (VC:L) assumes that the exposed alert content is sensitive but that the exposure is limited to a subset of alerts whose scope changed; if all alerts are affected or contain highly sensitive data, VC could be rated Higher.","The platform is assumed to be a multi-tenant or multi-organization security alerting system where visibility scoping is a core authorization mechanism.","No evidence of active exploitation or public PoC was found in the patch or metadata."],"fixSummary":"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.","patchSummary":"In app/alerting/alerting_core.py, within the _update_existing_alert function, two lines were added before the terminal-review-status conditional block: existing.owner_user_id and existing.owner_org_id are now assigned from the normalized incoming data on every duplicate update. Previously these fields were only set during initial alert creation and were not refreshed when a duplicate alert was ingested, leaving the stale scope in place.","credits":[{"lang":"en","value":"elhoim","type":"reporter"},{"lang":"en","value":"David Cruciani","type":"remediation developer"}],"cvssRationale":"AV:N - the platform is network-accessible. AC:L - the vulnerability is inherent in the duplicate-update code path; no special race or timing is needed. AT:N - no manipulation of the attack target is required. PR:L - an authenticated user with prior access to the alert is needed. UI:N - no user interaction beyond normal platform use. VC:L - confidential alert data is exposed to users outside the intended scope, but only for alerts affected by a scope change. VI:N, VA:N - no integrity or availability impact. SC:N, SI:N, SA:N - no secondary impacts. The overall severity is moderate: limited to a subset of alerts whose scope changed, requiring prior legitimate access.","ssvc":{"version":"2.0.3","role":"Supplier","timestamp":"2026-11-18T14:20:42Z","options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}]},"weaknessRationale":[{"cweId":"CWE-668","rationale":"The alert resource remains exposed to a broader set of users/organizations (the wrong sphere) because the ownership/visibility fields are not updated when the connector scope changes. The resource is accessible to entities outside its intended authorization boundary."},{"cweId":"CWE-862","rationale":"The system fails to enforce the current authorization scope on duplicate updates, effectively missing the authorization check that would restrict visibility to the correct set of users and organizations."}],"capecRationale":[{"capecId":"CAPEC-10","rationale":"The closest plausible attack pattern is leveraging a trusted relationship: a user or organization that previously had legitimate access to an alert (because it was within their scope) retains that access after the scope should have been narrowed. The attacker leverages the stale trust/visibility binding. This mapping is uncertain because the vulnerability is more of a stale-state authorization bug than an active exploitation of trust, but CAPEC-10 is the best available match for unauthorized access via a previously valid relationship."}],"modelComparison":{"selectedModel":"qwen3.8:27b","selectionMethod":"deterministic-consensus-v1","selectionNotice":"The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.","rankings":[{"model":"qwen3.8:27b","score":7,"agreementScore":11,"confidence":"medium","assumptionCount":5}],"potentialErrors":[]}}},"bcp-05-x-03":{"x_timeline":{"events":[{"type":"fix-developed","timestamp":"2026-11-06T09:54:31Z","description":"Corrective change authored (c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362): fix: [security] Refresh alert ownership scope on duplicate","references":["https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch"],"id":"evt-fix-developed-1"},{"id":"evt-fix-available-1","type":"fix-available","timestamp":"2026-11-18T14:20:07.629180Z","description":"Patch retrieved from the supplied URL; retrieval time is used as the default availability time.","references":["https://github.com/flowintel/flowintel/commit/c158e1bdcebda70dd4a1395f7ac1a0c14ac5d362.patch"]}]}}}}]},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-11-19T17:16:15.912845Z","id":"CVE-2026-133001","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-11-19T17:16:23.842Z"}}]}}}