Skip to main content
Menu
CVEs

CVE

Flowise token disclosure in MCP server via public chatflow endpoint

CVE-2026-130796

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

8.8HighCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
41/100 · provisional
33% of flowise downloads last week were affected versions (1.2K).npm, 3.5K downloads in the last 7 days, read Nov 16, 2026
None on Exploit-DB, Metasploit or GitHub

Summary

Flowise, an AI workflow tool, has an information disclosure flaw in its public chatflow endpoint that lets anyone on the network, without logging in, read MCP server bearer tokens. An attacker can use a leaked token to run chatflows, bypassing API key protection and using up the owner's model quota.

Written by a model from the sources below. Verify against them.

Original description

Flowise 3.1.3 through 3.1.4 contains an information disclosure vulnerability that allows unauthenticated attackers to read MCP server bearer tokens via the GET /api/v1/public-chatflows/:id handler. Attackers can use the leaked mcpServerConfig token on the POST /api/v1/mcp/:chatflowId route to invoke chatflows, bypassing API key protection and consuming the owner's model quota.

cve.now Index

41Pcve.now Index 41 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach10/20Affects npm packages
  • Severity8.8/10CVSS 8.8
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 86 if added to CISA KEV
  • Would score about 81 if CISA's SSVC rates exploitation active
  • Would score about 46 if advisories confirm default setups are exposed

Impact

  • Widely used

    flowise has 6.6k weekly downloads.Source: npmjs.com

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-130796 (Flowise 3.1.3 through 3.1.4 MCP Server Token Disclosure via Public Chatflow Endpoint), 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-130796 (entry last updated 2026-11-17):
Affected:
- npm package flowise: from 3.1.3, through 3.1.4
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130796 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130796 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/FlowiseAI/Flowise/blob/main/SECURITY.md
- https://flowiseai.com/sunset
- https://github.com/FlowiseAI/Flowise/blob/a65f81bb43ef66d3ce734bf0dff4223ae8041c95/packages/server/src/controllers/chatflows/index.ts#L229-L256
- https://github.com/FlowiseAI/Flowise/blob/a65f81bb43ef66d3ce734bf0dff4223ae8041c95/packages/server/src/database/entities/ChatFlow.ts#L64-L68
- https://github.com/FlowiseAI/Flowise/blob/a65f81bb43ef66d3ce734bf0dff4223ae8041c95/packages/server/src/services/mcp-server/index.ts#L223-L250
- https://www.vulncheck.com/advisories/flowise-3.1.3-through-3.1.4-mcp-server-token-disclosure-via-public-chatflow-endpoint
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-130796
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-130796"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • From 3.1.3 · through 3.1.4

    No fix released. The latest release, 3.1.4, is still affected.

Evidence 9

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

  1. Exploit

Other links · 5

  1. Advisory
  2. Repository
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130796

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

flowise (npm): from 3.1.3 through 3.1.4.Source: cve.now feed data

More CVEs