{"api_version":"1","generated_at":"2026-11-20T20:52:39+00:00","cve":"CVE-2026-133851","urls":{"html":"https://cve.report/CVE-2026-133851","api":"https://cve.report/api/cve/CVE-2026-133851.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-133851","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-133851"},"summary":{"title":"FlowIntel Alerting: Missing Private Case Authorization Check Allows Connector Owners to Access Revoked Case Data","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.\n\nThis 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.\n\nAdditionally, 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.\n\nImpact:\n- Unauthorized disclosure of private case data (review comments, raw payloads, action history) through alert endpoints.\n- Unauthorized modification of alert review status and creation of cases from alerts the user should no longer access.\n- Leakage of a competing case identifier to an unauthorized user during concurrent case-creation races.\n\nAffected versions: FlowIntel prior to 4.1.0.","state":"PUBLISHED","assigner":"CIRCL","published_at":"2026-11-20 15:17:53","updated_at":"2026-11-20 17:18:23"},"problem_types":["CWE-362","CWE-862","CWE-862 CWE-862 Missing Authorization","CWE-362 CWE-362 Concurrent Execution using Shared Resource with Inadequate Locking"],"metrics":[{"version":"4.0","source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","type":"Secondary","score":"5.3","severity":"MEDIUM","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","data":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","baseScore":5.3,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"LOW","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}},{"version":"4.0","source":"CNA","type":"CVSS","score":"5.3","severity":"MEDIUM","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","data":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"NETWORK","baseScore":5.3,"baseSeverity":"MEDIUM","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"LOW","vulnerabilityResponseEffort":"NOT_DEFINED"}}],"references":[{"url":"https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff","name":"https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff","refsource":"5a6e4751-2f3f-4070-9419-94fb35b644e8","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-133851","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-133851","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"flowintel","product":"flowintel","version":"affected 4.1.0 semver","platforms":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"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.","time":"","lang":"en"}],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"David Cruciani","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-133851","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-11-20T16:22:03.525644Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-11-20T16:34:09.703Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"cpes":["cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"],"modules":["app/alerting/alerting_core.py"],"product":"flowintel","programFiles":["app/alerting/alerting_core.py"],"repo":"https://github.com/flowintel/flowintel","vendor":"flowintel","versions":[{"lessThan":"4.1.0","status":"affected","version":"0","versionType":"semver"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*","vulnerable":true}],"negate":false,"operator":"OR"}]}],"credits":[{"lang":"en","type":"remediation developer","value":"David Cruciani"}],"descriptions":[{"lang":"en","value":"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.\n\nThis 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.\n\nAdditionally, 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.\n\nImpact:\n- Unauthorized disclosure of private case data (review comments, raw payloads, action history) through alert endpoints.\n- Unauthorized modification of alert review status and creation of cases from alerts the user should no longer access.\n- Leakage of a competing case identifier to an unauthorized user during concurrent case-creation races.\n\nAffected versions: FlowIntel prior to 4.1.0."}],"impacts":[{"capecId":"CAPEC-114","descriptions":[{"lang":"en","value":"CAPEC-114 Forced Browsing"}]}],"metrics":[{"cvssV4_0":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"NETWORK","baseScore":5.3,"baseSeverity":"MEDIUM","privilegesRequired":"LOW","providerUrgency":"NOT_DEFINED","subAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","userInteraction":"NONE","valueDensity":"NOT_DEFINED","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"LOW","vulnerabilityResponseEffort":"NOT_DEFINED"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]},{"format":"SSVC","other":{"content":{"options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"role":"Supplier","timestamp":"2026-11-20T14:20:59Z","version":"2.0.3"},"type":"SSVC"},"scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-862","description":"CWE-862 Missing Authorization","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-362","description":"CWE-362 Concurrent Execution using Shared Resource with Inadequate Locking","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-20T14:40:10.021Z","orgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","shortName":"CIRCL"},"references":[{"name":"Security patch","tags":["patch"],"url":"https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff"}],"solutions":[{"lang":"en","value":"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."}],"title":"FlowIntel Alerting: Missing Private Case Authorization Check Allows Connector Owners to Access Revoked Case Data","x_gcve":[{"extensions":{"bcp-05-x-01":{"ai_annotations":[{"ai_level":"generated","description":"Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.","gna_source":1,"models":[{"gna_source":1,"identifier":"qwen3.8:27b","name":"qwen3.8:27b","source":"ollama"}],"review_status":"full","scope":"record","tags":["ai-computer-assisted:llm-generated","ai-computer-assisted:classification"]}]},"bcp-05-x-02":{"x_patch2vuln":{"assumptions":["The affected version range is inferred from the explicit context (affected_version '0', fixed_version '4.1.0'); no explicit changelog or release notes are available to confirm the exact first vulnerable release.","The CAPEC-114 mapping is the closest available pattern; the actual attack is a logic flaw in authorization ordering rather than classic forced browsing, but no more specific CAPEC exists for missing authorization checks in API endpoints.","CVSS PR:L assumes the attacker must be an authenticated user with connector ownership; if the product allows unauthenticated access to alert endpoints, PR would be N, but the patch evidence (session-based auth, API keys in tests) supports authenticated access.","The TOCTOU component (CWE-362) requires a concurrent session to link the alert to a private case at the precise moment of the response; this is a secondary vector and the primary issue is the missing authorization check (CWE-862).","The commit message references 'Tool: Codex' which is noted as the AI tool used to assist in development; no credit is assigned for this as it is not a person or organization."],"capecRationale":[{"capecId":"CAPEC-114","rationale":"The attacker directly requests alert API endpoints (review, case-creation, read) using a known alert identifier. Because the authorization logic did not enforce private case membership, the server returned sensitive case data and accepted state-changing actions. This is the closest CAPEC to the observed pattern of accessing a resource by directly specifying its identifier without the required authorization context. Uncertainty: the attack does not involve guessing URLs but rather exploiting a logic flaw in an existing authorized endpoint; however, CAPEC-114 remains the best available match for direct resource access bypassing intended access controls."}],"commit":"68d85c78e464f023f9f77af9af39634d3b811fff","confidence":"medium","credits":[{"lang":"en","type":"remediation developer","value":"David Cruciani"}],"cvssRationale":"AV:N: The vulnerability is exploitable over the network via the FlowIntel web API. AC:L: No special race condition or complex setup is required; a connector owner whose case access was revoked can simply call the alert endpoints. AT:N: No manipulation of the target is needed. PR:L: The attacker must be an authenticated user with connector ownership of the alert. UI:N: No victim interaction is required. VC:L: Confidential impact is limited to alert-level data (review comments, raw payload, action history) rather than full case contents. VI:L: The attacker can modify review status and create cases, but cannot alter case data directly. VA:N: No availability impact. SC/SI/SA:N: No impact on other systems.","fixSummary":"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.","generatedAt":"2026-11-20T14:20:59.693658Z","generator":"patch2vuln.py","model":"qwen3.8:27b","modelComparison":{"potentialErrors":[],"rankings":[{"agreementScore":11,"assumptionCount":5,"confidence":"medium","model":"qwen3.8:27b","score":7}],"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."},"patchSha256":"e8226318f1d6462435435a1293e4a5091a59c7cd5671dbd98013ff3ae14d856a","patchSummary":"In can_user_view_alert, the private-case membership check was moved before the connector-ownership checks and made unconditional (no longer gated on case.is_private), so any user lacking case access is denied even if they own the connector. In update_review_status, a can_user_view_alert re-check is performed after the database commit and before returning the serialized alert, returning 403 if access was concurrently lost. In create_case_from_alert, after a competing claim is detected, a can_user_view_alert re-check gates the response that would otherwise return the winner's case_id. The unused import get_present_in_case was removed. 33 regression tests were added covering revoked access, connector scope, concurrent case-link transitions, and authorized-user preservation.","patchTruncated":false,"patches":[{"commit":"68d85c78e464f023f9f77af9af39634d3b811fff","date":"Tue, 17 Nov 2026 10:50:38 +0100","patchSha256":"e8226318f1d6462435435a1293e4a5091a59c7cd5671dbd98013ff3ae14d856a","retrievedAt":"2026-11-20T14:20:26.159139Z","source":"https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff","sourceUrl":"https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff","subject":"fix: [security] Enforce private case access for alert reviews"}],"source":"https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff","ssvc":{"options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"role":"Supplier","timestamp":"2026-11-20T14:20:59Z","version":"2.0.3"},"subject":"fix: [security] Enforce private case access for alert reviews","weaknessRationale":[{"cweId":"CWE-862","rationale":"The alert access function did not verify private case membership before granting access based on connector ownership. The authorization check for case-level access was either absent or insufficiently ordered, allowing a user with connector ownership to bypass the private case boundary."},{"cweId":"CWE-362","rationale":"The review-status update and case-creation paths did not re-verify authorization after the database commit, creating a TOCTOU window where a concurrent session could link the alert to a private case and the response would still disclose case data to an unauthorized user."}]}},"bcp-05-x-03":{"x_timeline":{"events":[{"description":"Corrective change authored (68d85c78e464f023f9f77af9af39634d3b811fff): fix: [security] Enforce private case access for alert reviews","id":"evt-fix-developed-1","references":["https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff"],"timestamp":"2026-11-17T09:50:38Z","type":"fix-developed"},{"description":"Patch retrieved from the supplied URL; retrieval time is used as the default availability time.","id":"evt-fix-available-1","references":["https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff"],"timestamp":"2026-11-20T14:20:26.159139Z","type":"fix-available"}]}}},"recordType":"advisory","vulnId":"GCVE-1-2026-20419"}]}},"cveMetadata":{"assignerOrgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","assignerShortName":"CIRCL","cveId":"CVE-2026-133851","datePublished":"2026-11-20T14:40:10.021Z","dateReserved":"2026-11-20T14:40:00.274Z","dateUpdated":"2026-11-20T16:34:09.703Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 15:17:53","lastModifiedDate":"2026-11-20 17:18:23","problem_types":["CWE-362","CWE-862","CWE-862 CWE-862 Missing Authorization","CWE-362 CWE-362 Concurrent Execution using Shared Resource with Inadequate Locking"],"metrics":{"cvssMetricV40":[{"source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","type":"Secondary","cvssData":{"version":"4.0","vectorString":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","baseScore":5.3,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"LOW","vulnAvailabilityImpact":"NONE","subConfidentialityImpact":"NONE","subIntegrityImpact":"NONE","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","confidentialityRequirement":"NOT_DEFINED","integrityRequirement":"NOT_DEFINED","availabilityRequirement":"NOT_DEFINED","modifiedAttackVector":"NOT_DEFINED","modifiedAttackComplexity":"NOT_DEFINED","modifiedAttackRequirements":"NOT_DEFINED","modifiedPrivilegesRequired":"NOT_DEFINED","modifiedUserInteraction":"NOT_DEFINED","modifiedVulnConfidentialityImpact":"NOT_DEFINED","modifiedVulnIntegrityImpact":"NOT_DEFINED","modifiedVulnAvailabilityImpact":"NOT_DEFINED","modifiedSubConfidentialityImpact":"NOT_DEFINED","modifiedSubIntegrityImpact":"NOT_DEFINED","modifiedSubAvailabilityImpact":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED"}}],"ssvcV203":[{"source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","ssvcData":{"timestamp":"2026-11-20T14:20:59Z","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"role":"Supplier","version":"2.0.3"}},{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-11-20T16:22:03.525644Z","id":"CVE-2026-133851","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"133851","Ordinal":"1","Title":"FlowIntel Alerting: Missing Private Case Authorization Check All","CVE":"CVE-2026-133851","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"133851","Ordinal":"1","NoteData":"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.\n\nThis 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.\n\nAdditionally, 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.\n\nImpact:\n- Unauthorized disclosure of private case data (review comments, raw payloads, action history) through alert endpoints.\n- Unauthorized modification of alert review status and creation of cases from alerts the user should no longer access.\n- Leakage of a competing case identifier to an unauthorized user during concurrent case-creation races.\n\nAffected versions: FlowIntel prior to 4.1.0.","Type":"Description","Title":"FlowIntel Alerting: Missing Private Case Authorization Check All"}]}}}