FlowIntel, a threat intelligence case management platform, contains an information disclosure vulnerability in its case serialization logic. When a case is rendered via the REST API or browser views, all connector instances associated with that case were included in the response regardless of the requesting user's permissions.
This means that any authenticated user with read access to a case could observe connector metadata belonging to other users (personal-scope connectors) or other organizations (org-scope connectors), including connector URLs, descriptions, UUIDs, and potentially embedded API credentials.
Preconditions:
- An authenticated user account with at least read access to the affected case
- The case must have connector instances attached that belong to other users or organizations
Impact:
- Disclosure of personal connector endpoints and credentials of other users
- Disclosure of organization-scoped connector metadata across organizational boundaries
- Enumeration of connector infrastructure (URLs, UUIDs, descriptions) not intended for the viewer
Affected versions: < 4.1.0
0.7% estimated probability of exploitation activity in the next 30 days; 54th 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-668Exposure of Resource to Wrong Sphere CWE-862Missing Authorization
Show the promptExplain CVE-2026-133844 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-133844?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-133844?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-133844 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.