{"api_version":"1","generated_at":"2026-11-20T19:06:12+00:00","cve":"CVE-2026-133852","urls":{"html":"https://cve.report/CVE-2026-133852","api":"https://cve.report/api/cve/CVE-2026-133852.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-133852","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-133852"},"summary":{"title":"flowintel Privileged Case Task Approval Bypass via Missing User Context and Template Creation","description":"flowintel is a case management application that enforces an approval workflow for tasks in privileged cases. Tasks in such cases are required to start in a Requested status, meaning they must receive explicit approval before becoming active.\n\nA logic flaw in the task-creation path allowed tasks to be initialized with a Created status (bypassing the approval step) in two scenarios:\n\n- When a task was created from a template and no acting user was supplied, the privileged-case check was skipped entirely, leaving the task in Created status.\n- When a case was created from a template, all copied tasks were unconditionally assigned the Created status regardless of the case's privileged designation.\n\nAn authenticated user with the ability to create tasks from templates or to instantiate cases from templates could therefore place tasks directly into an active state within privileged cases, circumventing the intended approval gate. This may expose restricted case content or permit actions that should require supervisory sign-off.\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-862","CWE-862 CWE-862 Missing Authorization"],"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/fd23a3cb577b1ac64b95f076578994188332b2d1","name":"https://github.com/flowintel/flowintel/commit/fd23a3cb577b1ac64b95f076578994188332b2d1","refsource":"5a6e4751-2f3f-4070-9419-94fb35b644e8","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-133852","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-133852","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 approval-workflow enforcement for privileged cases is now applied unconditionally at task creation time. The privileged-case check no longer depends on the presence of an acting user, and template-based case creation explicitly assigns the configured Requested status to tasks when the target case is privileged. Ordinary (non-privileged) cases retain the default Created status, preserving existing behavior.","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-133852","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","timestamp":"2026-11-20T16:22:14.438766Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-11-20T16:33:54.226Z","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/common_core.py","app/templating/TemplateCase.py"],"product":"flowintel","programFiles":[],"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 is a case management application that enforces an approval workflow for tasks in privileged cases. Tasks in such cases are required to start in a Requested status, meaning they must receive explicit approval before becoming active.\n\nA logic flaw in the task-creation path allowed tasks to be initialized with a Created status (bypassing the approval step) in two scenarios:\n\n- When a task was created from a template and no acting user was supplied, the privileged-case check was skipped entirely, leaving the task in Created status.\n- When a case was created from a template, all copied tasks were unconditionally assigned the Created status regardless of the case's privileged designation.\n\nAn authenticated user with the ability to create tasks from templates or to instantiate cases from templates could therefore place tasks directly into an active state within privileged cases, circumventing the intended approval gate. This may expose restricted case content or permit actions that should require supervisory sign-off.\n\nAffected versions: flowintel prior to 4.1.0."}],"impacts":[{"capecId":"CAPEC-108","descriptions":[{"lang":"en","value":"CAPEC-108 Parameter Tampering"}]}],"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:21:30Z","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"}]}],"providerMetadata":{"dateUpdated":"2026-11-20T14:40:25.523Z","orgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","shortName":"CIRCL"},"references":[{"name":"Security patch","tags":["patch"],"url":"https://github.com/flowintel/flowintel/commit/fd23a3cb577b1ac64b95f076578994188332b2d1"}],"solutions":[{"lang":"en","value":"The approval-workflow enforcement for privileged cases is now applied unconditionally at task creation time. The privileged-case check no longer depends on the presence of an acting user, and template-based case creation explicitly assigns the configured Requested status to tasks when the target case is privileged. Ordinary (non-privileged) cases retain the default Created status, preserving existing behavior."}],"title":"flowintel Privileged Case Task Approval Bypass via Missing User Context and Template Creation","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 'privileged case' designation implies a higher-sensitivity classification requiring supervisory approval; the exact business meaning is inferred from the code context and commit message.","PR:L assumes the attacker needs an authenticated account with template-creation permissions; the patch does not specify the exact role or permission required.","CAPEC-108 is the closest available mapping; the primary defect is a missing conditional check rather than active parameter manipulation, so the mapping is approximate.","The affected version range '0 to <4.1.0' is taken from the explicit analyst context; the patch itself does not encode version boundaries.","VC:L assumes that bypassing the approval step exposes task content that would otherwise be restricted; the patch does not detail what content is protected.","The commit message references 'Tool: Codex' which is noted as the AI tool used for implementation, not as a credit."],"capecRationale":[{"capecId":"CAPEC-108","rationale":"The vulnerability is triggered by the absence of a user parameter, which causes the privileged-case authorization check to be skipped. An attacker who can influence whether a user context is supplied (e.g., via an API endpoint that does not enforce authentication for this code path) effectively tampers with the parameter to bypass the control. This is the closest CAPEC available; the mapping is uncertain because the primary defect is a missing check rather than active parameter manipulation, but CAPEC-108 best captures the 'missing/absent parameter leads to skipped validation' pattern."}],"commit":"fd23a3cb577b1ac64b95f076578994188332b2d1","confidence":"medium","credits":[{"lang":"en","type":"remediation developer","value":"David Cruciani"}],"cvssRationale":"AV:N: flowintel is a web application accessible over the network. AC:L: the bypass is triggered simply by the absence of a user context or by using the template-creation path; no race condition or special timing is needed. AT:N: no manipulation of a separate attack target is required. PR:L: the attacker must be an authenticated user with permission to create tasks from templates or instantiate cases from templates. UI:N: no victim interaction is required. VC:L: tasks in privileged cases become immediately accessible without approval, potentially exposing restricted case content. VI:L: the integrity of the approval workflow is compromised; tasks are in an unauthorized state. VA:N: no availability impact. SC/SI/SA:N: no secondary impacts on other systems are evidenced.","fixSummary":"The approval-workflow enforcement for privileged cases is now applied unconditionally at task creation time. The privileged-case check no longer depends on the presence of an acting user, and template-based case creation explicitly assigns the configured Requested status to tasks when the target case is privileged. Ordinary (non-privileged) cases retain the default Created status, preserving existing behavior.","generatedAt":"2026-11-20T14:21:30.590126Z","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":"ef4bf88c9ae2f0d59b98cffbeb804fbbbeeb8017452a730e8c60200aa01ca687","patchSummary":"Two one-line changes were made. In app/case/common_core.py, the condition guarding the Requested-status assignment was changed from 'if current_user and case.privileged_case' to 'if case.privileged_case', removing the dependency on a non-null user. In app/templating/TemplateCase.py, the hardcoded 'status_id=1' in the task-copy constructor was replaced with a conditional expression that selects the configured TASK_REQUESTED status when the case is privileged and falls back to 1 otherwise.","patchTruncated":false,"patches":[{"commit":"fd23a3cb577b1ac64b95f076578994188332b2d1","date":"Tue, 17 Nov 2026 11:02:12 +0100","patchSha256":"ef4bf88c9ae2f0d59b98cffbeb804fbbbeeb8017452a730e8c60200aa01ca687","retrievedAt":"2026-11-20T14:21:01.216442Z","source":"https://github.com/flowintel/flowintel/commit/fd23a3cb577b1ac64b95f076578994188332b2d1","sourceUrl":"https://github.com/flowintel/flowintel/commit/fd23a3cb577b1ac64b95f076578994188332b2d1","subject":"fix: [security] Require initial approval for privileged"}],"source":"https://github.com/flowintel/flowintel/commit/fd23a3cb577b1ac64b95f076578994188332b2d1","ssvc":{"options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"partial"}],"role":"Supplier","timestamp":"2026-11-20T14:21:30Z","version":"2.0.3"},"subject":"fix: [security] Require initial approval for privileged","weaknessRationale":[{"cweId":"CWE-862","rationale":"The approval workflow (a form of authorization gate) for privileged-case tasks was not enforced under certain code paths (no user context, template-based creation), allowing tasks to skip the required approval step. The narrowest defensible CWE is Missing Authorization because the security control (approval) was simply absent in those paths."}]}},"bcp-05-x-03":{"x_timeline":{"events":[{"description":"Corrective change authored (fd23a3cb577b1ac64b95f076578994188332b2d1): fix: [security] Require initial approval for privileged","id":"evt-fix-developed-1","references":["https://github.com/flowintel/flowintel/commit/fd23a3cb577b1ac64b95f076578994188332b2d1"],"timestamp":"2026-11-17T10:02:12Z","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/fd23a3cb577b1ac64b95f076578994188332b2d1"],"timestamp":"2026-11-20T14:21:01.216442Z","type":"fix-available"}]}}},"recordType":"advisory","vulnId":"GCVE-1-2026-20420"}]}},"cveMetadata":{"assignerOrgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","assignerShortName":"CIRCL","cveId":"CVE-2026-133852","datePublished":"2026-11-20T14:40:25.523Z","dateReserved":"2026-11-20T14:40:19.091Z","dateUpdated":"2026-11-20T16:33:54.226Z","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-862","CWE-862 CWE-862 Missing Authorization"],"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:21:30Z","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:14.438766Z","id":"CVE-2026-133852","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"133852","Ordinal":"1","Title":"flowintel Privileged Case Task Approval Bypass via Missing User ","CVE":"CVE-2026-133852","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"133852","Ordinal":"1","NoteData":"flowintel is a case management application that enforces an approval workflow for tasks in privileged cases. Tasks in such cases are required to start in a Requested status, meaning they must receive explicit approval before becoming active.\n\nA logic flaw in the task-creation path allowed tasks to be initialized with a Created status (bypassing the approval step) in two scenarios:\n\n- When a task was created from a template and no acting user was supplied, the privileged-case check was skipped entirely, leaving the task in Created status.\n- When a case was created from a template, all copied tasks were unconditionally assigned the Created status regardless of the case's privileged designation.\n\nAn authenticated user with the ability to create tasks from templates or to instantiate cases from templates could therefore place tasks directly into an active state within privileged cases, circumventing the intended approval gate. This may expose restricted case content or permit actions that should require supervisory sign-off.\n\nAffected versions: flowintel prior to 4.1.0.","Type":"Description","Title":"flowintel Privileged Case Task Approval Bypass via Missing User "}]}}}