flowintel unauthorized deletion of evidence in privileged tasks
Affects FlowIntel versions before 4.1.0 when a privileged task is in the Requested, Rejected or Request Review state. Fixed in 4.1.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.1.0
- Who is exposed
- Specific setups only
Summary
FlowIntel, a case-management product, has a missing authorization check that lets any logged-in user with basic case membership, such as an editor or queuer, delete evidence files attached to privileged tasks in the Requested, Rejected, or Request Review state. An attacker can exploit this remotely over the network through the browser interface or the REST API, and doing so can destroy evidence, corrupt investigation timelines, and alter case history.
Written by a model
Original description
FlowIntel contains a missing authorization vulnerability in its task file deletion functionality. When a privileged task is in a restricted state (Requested, Rejected, or Request Review), any authenticated user with basic case membership (e.g., editor or queuer) was able to delete evidence files associated with that task via both the browser interface and the REST API. The deletion operation should have been restricted to users holding Admin, Case Admin, or Queue Admin roles.
The vulnerability affects the core file deletion logic, the browser-facing task endpoint, and the API task endpoint. No role-based restriction was enforced prior to performing disk removal, database record deletion, timeline event removal, or history log updates.
An attacker with a low-privilege case membership could destroy evidence files, corrupt investigation timelines, and alter case history, compromising the integrity of ongoing investigations.
Affected versions: FlowIntel prior to 4.1.0.
What to do
Check whether your setup matches what the bug needs.
The task is a privileged task in the Requested, Rejected or Request Review stateUpgrade to a fixed version: 4.1.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133839 (FlowIntel Missing Authorization Check Allows Unauthorized Deletion of Evidence Files from Restricted Privileged Tasks), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133839 (entry last updated 2026-11-20):
Affected:
- flowintel flowintel: fixed in 4.1.0
Fixed versions: 4.1.0.
Conditions (all must be true for the bug to be hit):
- The task is a privileged task in the Requested, Rejected or Request Review state (source: https://github.com/flowintel/flowintel/commit/7142a49da22f1079bcbd043bc33eb7cdfabc81a7)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-133839 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133839 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/flowintel/flowintel/commit/7142a49da22f1079bcbd043bc33eb7cdfabc81a7
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133839
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133839"}.Affected versions
- flowintel flowintelfixed in 4.1.0
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133839 |
| Record | NVD · CVE-2026-133839 |
| Other links 1 | |
| Patch | GitHub · flowintel/flowintel · Commit 7142a49d |
Questions about CVE-2026-133839
Is CVE-2026-133839 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Deleting evidence files from privileged tasks in the Requested, Rejected or Request Review states was not properly restricted by an authorization check. The fix requires Admin, Case Admin or Queue Admin roles to delete files from those tasks.
Source: github.com
Which versions are affected by CVE-2026-133839?
flowintel: before 4.1.0.
Source: cve.now feed data
Am I affected, and how do I check?
Versions of FlowIntel before 4.1.0 are in the affected range. The condition applies to privileged tasks in the Requested, Rejected or Request Review states, so check the installed FlowIntel version against 4.1.0 and whether such tasks exist.
Source: github.com
How do I fix CVE-2026-133839?
Upgrade FlowIntel to version 4.1.0 or later, which is the listed fixed version.
Source: github.com
Related
- CVE-2026-133663flowintel Insecure Direct Object Reference Allows Cross-Case Data Access and Modification
- CVE-2026-133847flowintel: Missing Authorization Check Allows Organization Admin to Edit Platform Admin Accounts via Browser Interface
- CVE-2026-133662flowintel Analyzer: Missing Authorization on Result Reads and Case/Task Writes (IDOR)
- CVE-2026-133848flowintel: Organization Admin Can Delete Platform Admin Accounts Due to Missing Privilege Hierarchy Check
- CVE-2026-133854flowintel: Information Disclosure of Classification Usage via Missing Access Control
- CVE-2026-133849flowintel: Insecure Direct Object Reference in Task Calendar Access Control
No corrections so far. Something wrong on this page? Report an error.