Skip to main content
Menu
CVEs

flowintel auth bypass in chatbot shared MCP session

CVE-2026-133853EUVD-2026-131593GHSA-W3Q8-9828-CGCRPublished , updated

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

Summary

FlowIntel's chatbot shares one session and process-wide environment variable across users, so a logged-in user can remotely have their identity applied to another user's chatbot tool calls. This can let a lower-privilege user read another user's data, such as private investigation cases, and can let revoked credentials keep working.

Written by a model

Original description

FlowIntel's chatbot component used a single shared MCP (Model Context Protocol) session and process-wide environment variable to pass per-user API credentials to a child process. Because the session and the ambient FLOWINTEL_API_KEY environment variable were shared across all concurrent requests, a user's authenticated identity could be applied to another user's tool invocation, or a stale/ambient credential could be inherited by a new request.

Preconditions:

  • An authenticated user with access to the chatbot interface.
  • Concurrent or overlapping chatbot tool invocations from different users, or a request made after another user's credentials were written to the process environment.

Impact:

  • A lower-privilege user could read data belonging to a higher-privilege user (e.g., private investigation cases).
  • A user whose session was invalidated (deleted, password changed, key revoked) could still operate under a previously cached ambient credential.
  • The parent process environment was mutated with user-specific secrets, creating a persistent credential leak surface.

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-133853 (FlowIntel Chatbot Shared MCP Session Allows Cross-User API Identity Confusion), 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-133853 (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-133853 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133853 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/9eec395cc73c6706362b2c22f1e264406eb8caf8
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-133853
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-133853"}.

Affected versions

cve.now Index

9Pof 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
  • Severity6/10CVSS 6.0
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 28 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-133853
RecordNVD · CVE-2026-133853
Other links 1
PatchGitHub · flowintel/flowintel · Commit 9eec395c

Questions about CVE-2026-133853

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

flowintel: before 4.1.0.

Source: cve.now feed data

How do I fix CVE-2026-133853?

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.