Skip to main content
Menu
CVEs

flowintel unauthorized data access via chatbot API

Affects FlowIntel versions before 4.1.0 that resolve note variable references in shared or imported notes. No vendor severity rating is given. Fixed in 4.1.0.

CVE-2026-133631Published , updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.1.0
Who is exposed
Specific setups only

Summary

FlowIntel contains several flaws. An authenticated user with access to a shared or imported note can reference private cases, pulling their data into AI reports, exports, and MISP sends, and a crafted case message can make the chatbot API tool call any FlowIntel endpoint, including administrative ones, to read restricted data or change it. Remote attackers with low-privilege logins can reach these flaws without any user action, and separately, any local user can see the Ollama token and case content in the process list during AI report generation.

Written by a model

Original description

FlowIntel contains multiple security flaws in its note variable resolution, chatbot API tooling, and AI report generation.

  • Note variable references (e.g. cross-case or cross-task lookups) were resolved using the viewing user's privileges rather than the destination case's audience. An authenticated user with access to a shared or imported note could embed references to private cases, causing sensitive case data to be pulled into AI report requests, exports, and MISP sends without the referenced case's audience having granted read access.
  • The chatbot API tool permitted the language model to invoke any FlowIntel API endpoint, including administrative routes and state-changing GET operations, without an allow-list or path validation. An attacker who can influence the model's instructions (e.g. via untrusted case content) could induce data modification or access restricted endpoints.
  • AI report generation passed the Ollama bearer token and full case content as command-line arguments to a child process, exposing them in the system process table to any local user.

Affected versions: FlowIntel prior to 4.1.0.

What to do

  1. Check whether your setup matches what the bug needs.

    Note variable references in shared or imported notes
  2. 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-133631 (FlowIntel Insecure Note Variable Resolution, Over-Permissive Chatbot API Access, and Credential Exposure in Process Arguments), 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-133631 (entry last updated 2026-11-20):
Affected:
- flowintel flowintel: fixed in 4.1.0
Fixed versions: 4.1.0.
Conditions (all must be true for the bug to be hit):
- Note variable references in shared or imported notes (source: https://github.com/flowintel/flowintel/commit/34d151b8dceb1fea925b353f04a9483aba0a22b1)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-133631 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133631 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/34d151b8dceb1fea925b353f04a9483aba0a22b1
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-133631
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-133631"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

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-133631
RecordNVD · CVE-2026-133631
Other links 1
PatchGitHub · flowintel/flowintel · Commit 34d151b8

Questions about CVE-2026-133631

Is CVE-2026-133631 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

What does this mean?

Note variables are resolved with the viewer's privileges, so references in shared or imported notes can pull private case data from cases the reader cannot access into AI report requests, exports and MISP sends. The chatbot model can also call FlowIntel API endpoints, including state-changing ones, beyond what was intended.

Source: github.com

Which versions are affected by CVE-2026-133631?

flowintel: before 4.1.0.

Source: cve.now feed data

Am I affected, and how do I check?

The affected range is FlowIntel versions before 4.1.0, and the exposure involves note variable references in shared or imported notes. To check, compare the installed FlowIntel version against 4.1.0 and review whether notes use variable references.

Source: github.com

How do I fix CVE-2026-133631?

The listed fixed version for this range is 4.1.0, so upgrade to 4.1.0 or later. The facts name no vendor patch identifiers.

Source: github.com

Why do the sources disagree?

The description refers to a local attack path, but the CVSS vector lists the attack vector as network (AV:N). The sources therefore disagree on how the bug can be reached.

Source: github.com

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