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
0.8% estimated probability of exploitation activity in the next 30 days; 56th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-200Exposure of Sensitive Information to an Unauthorized Actor CWE-862Missing Authorization
Show the promptExplain CVE-2026-133841 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-133841?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-133841?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-133841 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.