flowintel authorization bypass in task completion workflow
Affects flowintel versions before 4.1.0 for tasks in privileged cases that require approver review. Fixed in 4.1.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.1.0
- Who is exposed
- Specific setups only
Summary
flowintel has an authorization flaw in its task completion workflow that lets users with editor or queuer roles mark tasks as completed in privileged cases without the required approver review. An attacker with such a login can exploit it remotely over the network, through the web interface, the REST API, or by changing a task's status to "Finished."
Written by a model
Original description
flowintel contains an authorization bypass in its task completion workflow for privileged cases. Users with lower-privilege roles (editor, queuer) were able to mark tasks as completed without the required approver review (Admin, Case Admin, or Queue Admin), undermining the approval workflow.
The vulnerability was exploitable through multiple paths:
- Direct task completion via browser UI or REST API
- Changing a task's status to "Finished", which implicitly completed the task
- Creating a new task in a privileged case with the completed flag already set
- Using UUID aliases or Matrix delegation to reach the same endpoints
Preconditions:
- An authenticated user with at least editor or queuer role
- A privileged case with tasks in a non-completed state
Security impact:
- Bypass of the mandatory approver review process for privileged cases
- Unauthorized modification of task completion state
- Potential to mark sensitive work as finished without proper oversight
Affected versions: flowintel prior to 4.1.0
What to do
Check whether your setup matches what the bug needs.
Task belongs to a privileged case, where approver review is required.Upgrade 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-133837 (flowintel Missing Authorization Check Allows Non-Approvers to Complete 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-133837 (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):
- Task belongs to a privileged case, where approver review is required. (source: https://github.com/flowintel/flowintel/commit/dbd58d8762c824bcc27f912fe3f8497f416a7c16)
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-133837 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133837 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/dbd58d8762c824bcc27f912fe3f8497f416a7c16
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-133837
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-133837"}.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-133837 |
| Record | NVD · CVE-2026-133837 |
| Other links 1 | |
| Patch | GitHub · flowintel/flowintel · Commit dbd58d87 |
Questions about CVE-2026-133837
Is CVE-2026-133837 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?
A missing authorization check lets users who are not approvers complete privileged tasks that should need approver review first.
Source: github.com
Which versions are affected by CVE-2026-133837?
flowintel: before 4.1.0.
Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are flowintel releases before 4.1.0. The issue applies to tasks in privileged cases where the "Require approver review to complete privileged tasks" setting applies. Check the installed flowintel version and whether that setting is in use for the case.
Source: github.com
How do I fix CVE-2026-133837?
Upgrade flowintel to 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.