flowintel information disclosure in case serialization
- Exploited
- No known exploitation
- Fix
- Fixed in 4.1.0
- Who is exposed
- Not reported
Summary
FlowIntel, a threat intelligence case management platform, has a flaw that lets any logged-in user with read access to a case see connector details belonging to other users or organizations, including URLs, descriptions, UUIDs, and possibly embedded API credentials. An attacker can reach it remotely over the network with only a low-privilege login and no action from another user.
Written by a model
Original description
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
What to do
Upgrade to a fixed version: 4.1.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133844 (FlowIntel Case Serialization Exposes Unauthorized Connector Metadata to Authenticated Users), 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-133844 (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-133844 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133844 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/2ff99ca6ed81687fe28d57961d158e0804271416
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-133844
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-133844"}.Affected versions
- flowintel flowintelfixed in 4.1.0
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133844 |
| Record | NVD · CVE-2026-133844 |
| Other links 1 | |
| Patch | GitHub · flowintel/flowintel · Commit 2ff99ca6 |
Questions about CVE-2026-133844
Is CVE-2026-133844 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: cve.now feed data
Which versions are affected by CVE-2026-133844?
flowintel: before 4.1.0.
Source: cve.now feed data
How do I fix CVE-2026-133844?
Upgrade to a fixed version: 4.1.0.
Source: cve.now feed data
Related
- CVE-2026-133663flowintel Insecure Direct Object Reference Allows Cross-Case Data Access and Modification
- CVE-2026-133847flowintel: Missing Authorization Check Allows Organization Admin to Edit Platform Admin Accounts via Browser Interface
- CVE-2026-133662flowintel Analyzer: Missing Authorization on Result Reads and Case/Task Writes (IDOR)
- CVE-2026-133848flowintel: Organization Admin Can Delete Platform Admin Accounts Due to Missing Privilege Hierarchy Check
- CVE-2026-133854flowintel: Information Disclosure of Classification Usage via Missing Access Control
- CVE-2026-133849flowintel: Insecure Direct Object Reference in Task Calendar Access Control
No corrections so far. Something wrong on this page? Report an error.