Skip to content
Fencer Intel
medium 5.3

CVE-2026-133838 json

FlowIntel Missing Authorization on Restricted Task Modification Paths

published yesterday modified yesterday also EUVD-2026-131579

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

Summary

FlowIntel contains an authorization bypass that allows non-approver case members to modify restricted tasks (those in Requested, Rejected, or Request Review status) through several indirect code paths that lacked the required approver permission check.

Affected operations include: - Self-unassignment from a restricted task - Reordering tasks, including indirectly moving restricted sibling tasks - Linking or unlinking MISP objects and attributes to/from restricted tasks - Creating MISP objects or standalone attributes with task IDs referencing restricted tasks - Deleting MISP objects or attributes that are linked to restricted tasks - Executing modules on restricted tasks

A user with case member access (but without Admin, Case Admin, or Queue Admin privileges) could exploit these paths to alter the state of tasks that are supposed to be locked pending approval, effectively bypassing the intended approval workflow and potentially manipulating associated MISP data.

Affected versions: FlowIntel prior to 4.1.0

Patch / fix

  • flowintel flowintel 4.1.0

Is CVE-2026-133838 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.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-21).

CVSS scores

assigned by version score vector
CNA 4.0 5.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/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.