Skip to main content
Menu
CVEs

flowintel information disclosure of linked cases in case history

CVE-2026-133855EUVD-2026-131596GHSA-CG67-Q5P3-J6QQPublished , updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 4.1.0
Who is exposed
Not reported

Summary

flowintel has an information disclosure flaw in its case history feature, where the history output, including the web view, API, downloads, and report timelines, lists linked, unlinked, or forked cases without checking whether the user may view them. A logged-in user with access to any one case can remotely read its history and learn the identifiers and titles of other cases they should not be able to see.

Written by a model

Original description

flowintel contains an information disclosure vulnerability in its case history feature. When a user views the history of a case they are authorized to access, the history output includes references to other cases (linked, unlinked, or forked) without verifying whether the requesting user has permission to view those referenced cases. This exposes the identifiers and titles of cases that the user should not be able to discover.

The vulnerability affects multiple output paths:

  • Browser-based case history view
  • API history endpoint
  • Plain-text history download
  • Markdown history download
  • Report timeline generation

An authenticated user with access to any single case can enumerate the existence and identifiers of other cases by reading the history of a case they can access. This bypasses the intended per-case access control model and may reveal the existence of sensitive investigations, their identifiers, and associated metadata to unauthorized users.

The raw audit storage is not modified; the issue is solely in the presentation layer failing to filter references to inaccessible cases before returning history data to the user.

Affected versions: flowintel prior to 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-133855 (flowintel: Unauthorized Disclosure of Linked Case References in Case History), 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-133855 (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-133855 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133855 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/c44025ea68109996e3b1a0f01f6333caba190809
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-133855
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-133855"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133855
RecordNVD · CVE-2026-133855
Other links 1
PatchGitHub · flowintel/flowintel · Commit c44025ea

Questions about CVE-2026-133855

Is CVE-2026-133855 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-133855?

flowintel: before 4.1.0.

Source: cve.now feed data

How do I fix CVE-2026-133855?

Upgrade to a fixed version: 4.1.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.