Skip to content
Threat Brief

← All advisories

CVE-2026-133663

High 8.6No known exploitationFix available

flowintel Insecure Direct Object Reference Allows Cross-Case Data Access and Modification

Record last updated

CVSS score

8.6

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

None

No EPSS score available

CISA remediation deadline

None

Not in the KEV catalog

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. Affected operations include: - Reading task notes, subtasks, and URL tools by referencing their IDs without verifying they belong to the authorized task - Retrieving task assignees for a task belonging to a different case - Editing or deleting timeline events and timeline event links belonging to another case - Editing or removing case connectors belonging to another case - Invoking connector module operations (MISP, generic connectors, worker calls) by combining an authorized case with a connector link from a different case The 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. Security 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. Affected versions: flowintel prior to 4.1.0

Weakness: CWE-639, CWE-862

Patching and mitigation

Patch status
Fix available (source: CVE record (CIRCL))
Fix documented (source date)
Vendor solution
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.
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
flowintelflowintelall versions before 4.1.04.1.0CVE Program

Timeline

  1. Disclosure

    CVE record published by CIRCL

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (CIRCL)

    Source: CVE record (CIRCL) (opens in a new tab)

Vendor guidance and references