{"api_version":"1","generated_at":"2026-11-20T19:06:12+00:00","cve":"CVE-2026-133841","urls":{"html":"https://cve.report/CVE-2026-133841","api":"https://cve.report/api/cve/CVE-2026-133841.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-133841","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-133841"},"summary":{"title":"FlowIntel Information Disclosure of Linked Private Case Metadata via Unfiltered Case Serialization","description":"FlowIntel contains an authorization bypass in its case serialization logic that allows an authenticated user to view metadata of private cases they do not have access to.\n\nWhen a case is linked to another case, the JSON representation of the source case included the ID, title, and description of every linked case regardless of the requesting user's permissions. This affected multiple access paths:\n\n- Browser views (case detail, case info, search, calendar)\n- REST API endpoints (get case, list cases, search, title lookup, completed/not-completed lists)\n- Internal tooling and connector module context building\n\nAn attacker with valid credentials and access to any case that contains a link to a private case could enumerate the private case's identifier, title, and description without holding a membership or role on that private case. The exposure occurred because the serialization method did not receive or evaluate the acting user's identity before including linked-case data in the response.\n\nSecurity impact:\n- Disclosure of private case identifiers, titles, and descriptions to unauthorized users\n- Facilitation of further targeted attacks against the exposed private cases\n- Bypass of the intended per-case access control model\n\nAffected versions: FlowIntel prior to 4.1.0","state":"PUBLISHED","assigner":"CIRCL","published_at":"2026-11-20 15:17:51","updated_at":"2026-11-20 17:18:21"},"problem_types":["CWE-200","CWE-862","CWE-862 CWE-862 Missing Authorization","CWE-200 CWE-200 Exposure of Sensitive Information to an Unauthorized Actor"],"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:N/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:N/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":"NONE","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:N/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:N/VA:N/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"NONE","vulnerabilityResponseEffort":"NOT_DEFINED"}}],"references":[{"url":"https://github.com/flowintel/flowintel/commit/e6c780d97cd669500d05f1c911b2038f0dc91335","name":"https://github.com/flowintel/flowintel/commit/e6c780d97cd669500d05f1c911b2038f0dc91335","refsource":"5a6e4751-2f3f-4070-9419-94fb35b644e8","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-133841","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-133841","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 serialization method now accepts the acting user as a parameter and filters linked cases based on the user's authorization. When an authenticated user is provided, only linked cases the user is permitted to view are included. When no user is provided (internal or anonymous callers), the method fails closed by excluding all private linked cases. All call sites across browser views, API endpoints, calendar, search, tools, and internal core operations were updated to pass the resolved user identity, ensuring consistent enforcement regardless of the access path.","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-133841","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-11-20T16:20:30.849486Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-11-20T16:35:55.577Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"cpes":["cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"],"modules":["app/case","app/calendar","app/tools","app/db_class"],"product":"flowintel","programFiles":["app/db_class/db.py","app/case/case.py","app/case/case_api.py","app/case/CaseCore.py","app/calendar/calendar.py","app/tools/tools_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 contains an authorization bypass in its case serialization logic that allows an authenticated user to view metadata of private cases they do not have access to.\n\nWhen a case is linked to another case, the JSON representation of the source case included the ID, title, and description of every linked case regardless of the requesting user's permissions. This affected multiple access paths:\n\n- Browser views (case detail, case info, search, calendar)\n- REST API endpoints (get case, list cases, search, title lookup, completed/not-completed lists)\n- Internal tooling and connector module context building\n\nAn attacker with valid credentials and access to any case that contains a link to a private case could enumerate the private case's identifier, title, and description without holding a membership or role on that private case. The exposure occurred because the serialization method did not receive or evaluate the acting user's identity before including linked-case data in the response.\n\nSecurity impact:\n- Disclosure of private case identifiers, titles, and descriptions to unauthorized users\n- Facilitation of further targeted attacks against the exposed private cases\n- Bypass of the intended per-case access control model\n\nAffected versions: FlowIntel prior to 4.1.0"}],"impacts":[{"capecId":"CAPEC-12","descriptions":[{"lang":"en","value":"CAPEC-12 Application Metadata Discovery"}]}],"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:N/VA:N/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"LOW","vulnIntegrityImpact":"NONE","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:27:14Z","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-200","description":"CWE-200 Exposure of Sensitive Information to an Unauthorized Actor","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-20T14:37:27.260Z","orgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","shortName":"CIRCL"},"references":[{"name":"Security patch","tags":["patch"],"url":"https://github.com/flowintel/flowintel/commit/e6c780d97cd669500d05f1c911b2038f0dc91335"}],"solutions":[{"lang":"en","value":"The serialization method now accepts the acting user as a parameter and filters linked cases based on the user's authorization. When an authenticated user is provided, only linked cases the user is permitted to view are included. When no user is provided (internal or anonymous callers), the method fails closed by excluding all private linked cases. All call sites across browser views, API endpoints, calendar, search, tools, and internal core operations were updated to pass the resolved user identity, ensuring consistent enforcement regardless of the access path."}],"title":"FlowIntel Information Disclosure of Linked Private Case Metadata via Unfiltered Case Serialization","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 assumed to be all versions prior to 4.1.0 based on the explicit context; no earlier version boundary is specified in the patch.","PR:L assumes the attacker needs at minimum a low-privilege account with access to one case that is linked to a private case; if no such link exists in a deployment, the vulnerability is not triggerable.","VC:L assumes that exposure of case ID, title, and description constitutes a low (not high) confidentiality impact; if titles or descriptions contain highly sensitive operational details, impact could be higher.","CAPEC-12 is the closest available mapping but does not precisely model authorization-failure-driven relational data exposure; uncertainty is noted in the CAPEC rationale.","The patch does not indicate whether the vulnerability was reported externally or found internally; no finder or reporter credit is assigned.","UI:N assumes the attacker initiates the request themselves; no victim interaction is required."],"capecRationale":[{"capecId":"CAPEC-12","rationale":"The closest available CAPEC pattern. An authenticated user makes a legitimate request for a case they can access, and the application's response inadvertently discloses metadata (IDs, titles, descriptions) of private cases the user is not authorized to view. The uncertainty is that CAPEC-12 typically refers to version or configuration metadata discovery, whereas this is an authorization-failure-driven data exposure. No CAPEC specifically models 'information disclosure through unfiltered relational data in API responses,' making CAPEC-12 the best available approximation."}],"commit":"e6c780d97cd669500d05f1c911b2038f0dc91335","confidence":"medium","credits":[{"lang":"en","type":"remediation developer","value":"David Cruciani"}],"cvssRationale":"AV:N - exploitable over the network via HTTP API or browser. AC:L - no special race conditions or complex setup; any user with access to a case linked to a private case triggers the disclosure. AT:N - no attack-target manipulation required. PR:L - requires a low-privilege authenticated user with access to at least one case that has a link to a private case. UI:N - no victim interaction beyond the attacker's own request. VC:L - limited confidentiality impact: case IDs, titles, and descriptions are exposed, but full case content, tasks, and objects are not. VI:N, VA:N - no integrity or availability impact. SC:N, SI:N, SA:N - no impact on subsequent components; the data belongs to the same application.","fixSummary":"The serialization method now accepts the acting user as a parameter and filters linked cases based on the user's authorization. When an authenticated user is provided, only linked cases the user is permitted to view are included. When no user is provided (internal or anonymous callers), the method fails closed by excluding all private linked cases. All call sites across browser views, API endpoints, calendar, search, tools, and internal core operations were updated to pass the resolved user identity, ensuring consistent enforcement regardless of the access path.","generatedAt":"2026-11-20T14:27:14.511240Z","generator":"patch2vuln.py","model":"qwen3.8:27b","modelComparison":{"potentialErrors":[],"rankings":[{"agreementScore":11,"assumptionCount":6,"confidence":"medium","model":"qwen3.8:27b","score":6}],"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":"727879b87960655e2b7060531b0c78ec1b9497395c83f375c43626290bf5334c","patchSummary":"Modified the case serialization method in the database model to accept an optional user parameter. When a user is supplied and authenticated, linked cases are filtered through an existing permission-check function. When no user is supplied, only non-private linked cases are returned. Updated approximately 15 call sites across app/case/case.py, app/case/case_api.py, app/case/CaseCore.py, app/calendar/calendar.py, app/tools/tools_core.py, and app/db_class/db.py to pass the current or API-resolved user. In the API single-case endpoint, the user is now explicitly extracted from API headers and passed to both the authorization check and the serializer. Added a new test file (tests/case/test_case_link_visibility.py) with 171 lines covering API and browser filtering, identity separation between session and API key, Matrix delegation, anonymous/anonymous-user fail-closed behavior, and dynamic permission changes.","patchTruncated":false,"patches":[{"commit":"e6c780d97cd669500d05f1c911b2038f0dc91335","date":"Thu, 12 Nov 2026 17:30:22 +0100","patchSha256":"727879b87960655e2b7060531b0c78ec1b9497395c83f375c43626290bf5334c","retrievedAt":"2026-11-20T14:26:38.228863Z","source":"https://github.com/flowintel/flowintel/commit/e6c780d97cd669500d05f1c911b2038f0dc91335","sourceUrl":"https://github.com/flowintel/flowintel/commit/e6c780d97cd669500d05f1c911b2038f0dc91335","subject":"fix: [security] Filter linked cases by viewer permissions"}],"source":"https://github.com/flowintel/flowintel/commit/e6c780d97cd669500d05f1c911b2038f0dc91335","ssvc":{"options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"role":"Supplier","timestamp":"2026-11-20T14:27:14Z","version":"2.0.3"},"subject":"fix: [security] Filter linked cases by viewer permissions","weaknessRationale":[{"cweId":"CWE-862","rationale":"The case serialization method did not perform an authorization check on linked private cases before including their metadata in the response. The permission model existed for direct case access but was not applied to transitively referenced (linked) case data."},{"cweId":"CWE-200","rationale":"The result of the missing authorization check was the exposure of private case IDs, titles, and descriptions to users who had no membership or role on those private cases."}]}},"bcp-05-x-03":{"x_timeline":{"events":[{"description":"Corrective change authored (e6c780d97cd669500d05f1c911b2038f0dc91335): fix: [security] Filter linked cases by viewer permissions","id":"evt-fix-developed-1","references":["https://github.com/flowintel/flowintel/commit/e6c780d97cd669500d05f1c911b2038f0dc91335"],"timestamp":"2026-11-12T16:30:22Z","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/e6c780d97cd669500d05f1c911b2038f0dc91335"],"timestamp":"2026-11-20T14:26:38.228863Z","type":"fix-available"}]}}},"recordType":"advisory","vulnId":"GCVE-1-2026-20411"}]}},"cveMetadata":{"assignerOrgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","assignerShortName":"CIRCL","cveId":"CVE-2026-133841","datePublished":"2026-11-20T14:37:27.260Z","dateReserved":"2026-11-20T14:37:21.756Z","dateUpdated":"2026-11-20T16:35:55.577Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 15:17:51","lastModifiedDate":"2026-11-20 17:18:21","problem_types":["CWE-200","CWE-862","CWE-862 CWE-862 Missing Authorization","CWE-200 CWE-200 Exposure of Sensitive Information to an Unauthorized Actor"],"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:N/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":"NONE","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:27:14Z","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"role":"Supplier","version":"2.0.3"}},{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-11-20T16:20:30.849486Z","id":"CVE-2026-133841","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"133841","Ordinal":"1","Title":"FlowIntel Information Disclosure of Linked Private Case Metadata","CVE":"CVE-2026-133841","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"133841","Ordinal":"1","NoteData":"FlowIntel contains an authorization bypass in its case serialization logic that allows an authenticated user to view metadata of private cases they do not have access to.\n\nWhen a case is linked to another case, the JSON representation of the source case included the ID, title, and description of every linked case regardless of the requesting user's permissions. This affected multiple access paths:\n\n- Browser views (case detail, case info, search, calendar)\n- REST API endpoints (get case, list cases, search, title lookup, completed/not-completed lists)\n- Internal tooling and connector module context building\n\nAn attacker with valid credentials and access to any case that contains a link to a private case could enumerate the private case's identifier, title, and description without holding a membership or role on that private case. The exposure occurred because the serialization method did not receive or evaluate the acting user's identity before including linked-case data in the response.\n\nSecurity impact:\n- Disclosure of private case identifiers, titles, and descriptions to unauthorized users\n- Facilitation of further targeted attacks against the exposed private cases\n- Bypass of the intended per-case access control model\n\nAffected versions: FlowIntel prior to 4.1.0","Type":"Description","Title":"FlowIntel Information Disclosure of Linked Private Case Metadata"}]}}}