CVE-2026-133663: flowintel Insecure Direct Object Reference Allows Cross-Case Data Access and Modification

Published Nov 20, 2026
·
Updated

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

Affected Software

1 affected component
FlowIntel FlowIntel<4.1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade flowintel to a version that resolves this vulnerability.

    Fixed in 4.1.0

Event History

Nov 20, 2026
CVE Published
via MITRE·10:58 AM
Data Sourced
via MITRE·10:58 AM
RemedyDescriptionWeakness
Data Sourced
via OSV·10:58 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:18 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated user who has access to at least one case or task can exploit the issue. The user must be able to supply identifiers for child records associated with other cases or tasks.

2

What data and actions are exposed?

Affected operations include reading task notes, subtasks, URL tools, and task assignees across case boundaries. An attacker may also edit or delete timeline events and links, alter or remove case connectors, and invoke connector module operations using a connector link from another case.

3

Does exploitation require user interaction or special conditions?

No user interaction is required, and the listed attack vector is network-based with low attack complexity. The attacker does need prior authenticated access to a case or task.

4

How can defenders identify potentially affected activity?

Review application and API logs for requests where the authorized case or task in the URL differs from the case or task that owns the referenced child-record or connector-link identifier. Pay particular attention to cross-case reads and modifications involving task notes, subtasks, URL tools, assignees, timeline events, connectors, and connector module calls.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203