{"api_version":"1","generated_at":"2026-11-20T15:21:36+00:00","cve":"CVE-2026-133663","urls":{"html":"https://cve.report/CVE-2026-133663","api":"https://cve.report/api/cve/CVE-2026-133663.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-133663","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-133663"},"summary":{"title":"flowintel Insecure Direct Object Reference Allows Cross-Case Data Access and Modification","description":"flowintel contains an Insecure Direct Object Reference (IDOR) vulnerability affecting multiple endpoints that manage child records of cases and tasks. An authenticated user with access to one case or task could read or modify records belonging to other cases by supplying identifiers of those records directly in the request.\n\nAffected operations include:\n- Reading task notes, subtasks, and URL tools by referencing their IDs without verifying they belong to the authorized task\n- Retrieving task assignees for a task belonging to a different case\n- Editing or deleting timeline events and timeline event links belonging to another case\n- Editing or removing case connectors belonging to another case\n- Invoking connector module operations (MISP, generic connectors, worker calls) by combining an authorized case with a connector link from a different case\n\nThe root cause is that the application authorized the parent resource (case or task) in the URL but then fetched or operated on the child record independently without verifying the child's ownership relationship to the authorized parent.\n\nSecurity impact: an authenticated user can exfiltrate sensitive threat intelligence data from cases they do not have access to, and can modify or delete timeline entries, connector configurations, and other records in unauthorized cases, leading to data integrity loss and potential disruption of incident response workflows.\n\nAffected versions: flowintel prior to 4.1.0","state":"PUBLISHED","assigner":"CIRCL","published_at":"2026-11-20 11:18:34","updated_at":"2026-11-20 11:18:34"},"problem_types":["CWE-639","CWE-862","CWE-639 CWE-639 Authorization Bypass Through User-Controlled Key","CWE-862 CWE-862 Missing Authorization"],"metrics":[{"version":"4.0","source":"5a6e4751-2f3f-4070-9419-94fb35b644e8","type":"Secondary","score":"8.6","severity":"HIGH","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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:H/VI:H/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":8.6,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","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":"8.6","severity":"HIGH","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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":8.6,"baseSeverity":"HIGH","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:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnerabilityResponseEffort":"NOT_DEFINED"}}],"references":[{"url":"https://github.com/flowintel/flowintel/commit/fecba79506dea2886118fe5cd686d4edfdef60ae","name":"https://github.com/flowintel/flowintel/commit/fecba79506dea2886118fe5cd686d4edfdef60ae","refsource":"5a6e4751-2f3f-4070-9419-94fb35b644e8","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-133663","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-133663","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 ownership validation by requiring the authorized parent case or task ID in every core method that reads or writes child records. Before returning data or performing writes, each child record's case_id or task_id is explicitly compared against the resolved parent. Mismatched records are rejected with a 404 or 403 response. Connector module context building now verifies connector-to-case ownership before preparing module data, resolving credentials, or executing sync operations. Instance visibility checks are applied consistently across both web and API routes.","time":"","lang":"en"}],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"elhoim","lang":"en"},{"source":"CNA","value":"David Cruciani","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"cpes":["cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"],"modules":["app/case/CaseCore.py","app/case/case.py","app/case/case_api.py","app/case/case_misp.py","app/case/task_api.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":"reporter","value":"elhoim"},{"lang":"en","type":"remediation developer","value":"David Cruciani"}],"descriptions":[{"lang":"en","value":"flowintel contains an Insecure Direct Object Reference (IDOR) vulnerability affecting multiple endpoints that manage child records of cases and tasks. An authenticated user with access to one case or task could read or modify records belonging to other cases by supplying identifiers of those records directly in the request.\n\nAffected operations include:\n- Reading task notes, subtasks, and URL tools by referencing their IDs without verifying they belong to the authorized task\n- Retrieving task assignees for a task belonging to a different case\n- Editing or deleting timeline events and timeline event links belonging to another case\n- Editing or removing case connectors belonging to another case\n- Invoking connector module operations (MISP, generic connectors, worker calls) by combining an authorized case with a connector link from a different case\n\nThe root cause is that the application authorized the parent resource (case or task) in the URL but then fetched or operated on the child record independently without verifying the child's ownership relationship to the authorized parent.\n\nSecurity impact: an authenticated user can exfiltrate sensitive threat intelligence data from cases they do not have access to, and can modify or delete timeline entries, connector configurations, and other records in unauthorized cases, leading to data integrity loss and potential disruption of incident response workflows.\n\nAffected versions: flowintel prior to 4.1.0"}],"impacts":[{"capecId":"CAPEC-1","descriptions":[{"lang":"en","value":"CAPEC-1 Tamper with URLs"}]}],"metrics":[{"cvssV4_0":{"Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","Safety":"NOT_DEFINED","attackComplexity":"LOW","attackRequirements":"NONE","attackVector":"NETWORK","baseScore":8.6,"baseSeverity":"HIGH","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:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0","vulnAvailabilityImpact":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","vulnerabilityResponseEffort":"NOT_DEFINED"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]},{"format":"SSVC","other":{"content":{"options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"total"}],"role":"Supplier","timestamp":"2026-11-20T10:47:07Z","version":"2.0.3"},"type":"SSVC"},"scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-639","description":"CWE-639 Authorization Bypass Through User-Controlled Key","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-862","description":"CWE-862 Missing Authorization","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-20T10:58:03.710Z","orgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","shortName":"CIRCL"},"references":[{"name":"Security patch","tags":["patch"],"url":"https://github.com/flowintel/flowintel/commit/fecba79506dea2886118fe5cd686d4edfdef60ae"}],"solutions":[{"lang":"en","value":"The fix enforces ownership validation by requiring the authorized parent case or task ID in every core method that reads or writes child records. Before returning data or performing writes, each child record's case_id or task_id is explicitly compared against the resolved parent. Mismatched records are rejected with a 404 or 403 response. Connector module context building now verifies connector-to-case ownership before preparing module data, resolving credentials, or executing sync operations. Instance visibility checks are applied consistently across both web and API routes."}],"title":"flowintel Insecure Direct Object Reference Allows Cross-Case Data Access and Modification","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 earlier version boundary is confirmed.","PR:L assumes the attacker needs at least one valid case or task membership; the patch does not clarify whether anonymous access is possible.","CAPEC-1 (Tamper with URLs) is the closest available pattern; the actual attack is parameter substitution in REST endpoints rather than classic URL tampering, but no more specific CAPEC exists for IDOR via REST identifiers.","VC:H and VI:H assume the data in other cases is sensitive and that modification/deletion constitutes full integrity loss; the patch does not specify data classification.","The patch does not indicate whether the vulnerability was disclosed publicly or under embargo; exploitation status is assumed to be 'none' based on absence of evidence.","Instance visibility enforcement (can_interact_with_case_connector) was added to the API route in case_api.py but was already present in case_misp.py; the patch ensures consistency rather than introducing a new check in all locations."],"capecRationale":[{"capecId":"CAPEC-1","rationale":"The attacker manipulates URL path parameters or query string identifiers (note_id, subtask_id, url_tool_id, connector instance ID, timeline event ID) to reference objects belonging to other cases or tasks. The application did not validate that the referenced object belonged to the authorized parent, allowing cross-tenant data access. This is the closest CAPEC pattern; the attack does not involve protocol-level tampering but rather parameter substitution in REST-style URLs, which falls under the broader 'tamper with URLs' category."}],"commit":"fecba79506dea2886118fe5cd686d4edfdef60ae","confidence":"high","credits":[{"lang":"en","type":"reporter","value":"elhoim"},{"lang":"en","type":"remediation developer","value":"David Cruciani"}],"cvssRationale":"AV:N - exploitable over the network via HTTP API. AC:L - the attacker only needs to know or enumerate valid child record IDs; no special race conditions or complex setup required. AT:N - no attack target manipulation needed. PR:L - requires an authenticated user with access to at least one case or task. UI:N - no user interaction required. VC:H - full read access to sensitive threat intelligence data in other cases. VI:H - ability to modify or delete timeline events, links, and connectors in other cases. VA:N - no denial-of-service impact. SC/SI/SA:N - impact is confined to the flowintel application's own data store; no external system impact is evidenced.","fixSummary":"The fix enforces ownership validation by requiring the authorized parent case or task ID in every core method that reads or writes child records. Before returning data or performing writes, each child record's case_id or task_id is explicitly compared against the resolved parent. Mismatched records are rejected with a 404 or 403 response. Connector module context building now verifies connector-to-case ownership before preparing module data, resolving credentials, or executing sync operations. Instance visibility checks are applied consistently across both web and API routes.","generatedAt":"2026-11-20T10:47:07.135346Z","generator":"patch2vuln.py","model":"qwen3.8:27b","modelComparison":{"potentialErrors":[],"rankings":[{"agreementScore":11,"assumptionCount":6,"confidence":"high","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":"5d78368cb0ddd8fd9dab90b7c709b83b5aff34787ec2c25e7ba984947f4454c9","patchSummary":"Added case_id or task_id ownership checks in CaseCore.py methods (remove_connector, edit_connector, edit_timeline_event, edit_timeline_event_link, _build_case_connector_module_context) by passing the authorized parent ID and comparing it against the child record's foreign key. Updated case.py get_assigned_users to verify task.case_id matches the resolved case. Updated case_api.py EditConnectorsCase and RemoveConnectors to validate connector ownership and instance visibility before delegating. Updated case_misp.py timeline and connector endpoints to pass case.id to core methods. Updated task_api.py note, subtask, and URL-tool GET handlers to verify the child's task_id matches the authorized task.","patchTruncated":false,"patches":[{"commit":"fecba79506dea2886118fe5cd686d4edfdef60ae","date":"Fri, 30 Oct 2026 14:58:13 +0100","patchSha256":"5d78368cb0ddd8fd9dab90b7c709b83b5aff34787ec2c25e7ba984947f4454c9","retrievedAt":"2026-11-20T10:46:36.448315Z","source":"https://github.com/flowintel/flowintel/commit/fecba79506dea2886118fe5cd686d4edfdef60ae.patch","sourceUrl":"https://github.com/flowintel/flowintel/commit/fecba79506dea2886118fe5cd686d4edfdef60ae.patch","subject":"fix: [security] Child records stay bound to their authorised"}],"source":"https://github.com/flowintel/flowintel/commit/fecba79506dea2886118fe5cd686d4edfdef60ae.patch","ssvc":{"options":[{"Exploitation":"none"},{"Automatable":"yes"},{"Technical Impact":"total"}],"role":"Supplier","timestamp":"2026-11-20T10:47:07Z","version":"2.0.3"},"subject":"fix: [security] Child records stay bound to their authorised","weaknessRationale":[{"cweId":"CWE-639","rationale":"The vulnerability is a classic IDOR: user-supplied identifiers for child records (notes, subtasks, connectors, timeline events) are used to fetch or modify objects without verifying the object belongs to the authorized parent case or task. The authorization check on the parent does not constrain the child lookup."},{"cweId":"CWE-862","rationale":"Several endpoints performed the operation on a child record without any ownership or authorization check tying the record to the user's authorized case, effectively missing the authorization step for the specific object being accessed."}]}},"bcp-05-x-03":{"x_timeline":{"events":[{"description":"Corrective change authored (fecba79506dea2886118fe5cd686d4edfdef60ae): fix: [security] Child records stay bound to their authorised","id":"evt-fix-developed-1","references":["https://github.com/flowintel/flowintel/commit/fecba79506dea2886118fe5cd686d4edfdef60ae.patch"],"timestamp":"2026-10-30T13:58:13Z","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/fecba79506dea2886118fe5cd686d4edfdef60ae.patch"],"timestamp":"2026-11-20T10:46:36.448315Z","type":"fix-available"}]}}},"recordType":"advisory","vulnId":"GCVE-1-2026-20404"}]}},"cveMetadata":{"assignerOrgId":"5a6e4751-2f3f-4070-9419-94fb35b644e8","assignerShortName":"CIRCL","cveId":"CVE-2026-133663","datePublished":"2026-11-20T10:58:03.710Z","dateReserved":"2026-11-20T10:58:01.964Z","dateUpdated":"2026-11-20T10:58:03.710Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 11:18:34","lastModifiedDate":"2026-11-20 11:18:34","problem_types":["CWE-639","CWE-862","CWE-639 CWE-639 Authorization Bypass Through User-Controlled Key","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:H/VI:H/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":8.6,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"NONE","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","vulnIntegrityImpact":"HIGH","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-20T10:47:07Z","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"role":"Supplier","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"133663","Ordinal":"1","Title":"flowintel Insecure Direct Object Reference Allows Cross-Case Dat","CVE":"CVE-2026-133663","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"133663","Ordinal":"1","NoteData":"flowintel contains an Insecure Direct Object Reference (IDOR) vulnerability affecting multiple endpoints that manage child records of cases and tasks. An authenticated user with access to one case or task could read or modify records belonging to other cases by supplying identifiers of those records directly in the request.\n\nAffected operations include:\n- Reading task notes, subtasks, and URL tools by referencing their IDs without verifying they belong to the authorized task\n- Retrieving task assignees for a task belonging to a different case\n- Editing or deleting timeline events and timeline event links belonging to another case\n- Editing or removing case connectors belonging to another case\n- Invoking connector module operations (MISP, generic connectors, worker calls) by combining an authorized case with a connector link from a different case\n\nThe root cause is that the application authorized the parent resource (case or task) in the URL but then fetched or operated on the child record independently without verifying the child's ownership relationship to the authorized parent.\n\nSecurity impact: an authenticated user can exfiltrate sensitive threat intelligence data from cases they do not have access to, and can modify or delete timeline entries, connector configurations, and other records in unauthorized cases, leading to data integrity loss and potential disruption of incident response workflows.\n\nAffected versions: flowintel prior to 4.1.0","Type":"Description","Title":"flowintel Insecure Direct Object Reference Allows Cross-Case Dat"}]}}}