Flowintel up to 3.3.0 My Assignment User API Endpoint user_id privileges management

Summaryinfo

A vulnerability marked as problematic has been reported in Flowintel up to 3.3.0. The affected element is an unknown function of the component My Assignment User API Endpoint. The manipulation of the argument user_id leads to privileges management. This vulnerability is documented as CVE-2026-81819. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Flowintel up to 3.3.0. This issue affects an unknown code of the component My Assignment User API Endpoint. The manipulation of the argument user_id with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality. The summary by CVE is:

Affected versions of Flowintel expose the /my_assignment/user API endpoint to any authenticated API user. The endpoint accepts a user_id parameter identifying the user whose assignments should be returned, but previously had no role restriction beyond general API authentication. As a result, a lower-privileged authenticated user could potentially query another user’s assignment information by supplying that user’s identifier. The fix changes: method_decorators = [api_required] to: method_decorators = [admin_or_org_admin_required, api_required] so only administrators or organization administrators can perform cross-user assignment queries. Version impacted =>3.3.0

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-81819 since 08/27/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Applying the patch 10ec32e7baa0fa12ffb83bec36d1b4749a428b5c is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• Flowintel

Version

• 3.0
• 3.1
• 3.2
• 3.3.0

Website

• Product: https://github.com/flowintel/flowintel/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion