Skip to content
Fencer Intel
high 7.1

CVE-2026-133837 json

flowintel Missing Authorization Check Allows Non-Approvers to Complete Privileged Tasks

published yesterday modified yesterday also EUVD-2026-131578

cvss
7.1
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

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

Patch / fix

  • flowintel flowintel 4.1.0

Is CVE-2026-133837 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
yesterday

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-21).

CVSS scores

assigned by version score vector
CNA 4.0 7.1 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Affected products

  • flowintel flowintel

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.