All vulnerabilities

Servers and applications

GHSA-c2c9-mfw7-p8hw

Cross-Workspace Chatflow Disclosure via chatflows/apikey Endpoint Returns All Unprotected Chatflows

Severity
Medium 5.3
Published
14 May 2026
Last changed
14 May 2026
Added to UpHeron
1 Nov 2026
Fixed in
3.1.2
Weakness
Incorrect authorization (CWE-863)
Attack
Over the network · Needs a user account · No user action needed
Attacker can
Read some data
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Sources
Project advisories (GitHub)

Description

The /api/v1/chatflows/apikey/:apikey endpoint (whitelisted, accessible with API key auth only) returns all chatflows bound to the provided API key AND all chatflows across the entire system that have no API key assigned. This crosses workspace boundaries, allowing a user in Workspace A who has a valid API key to read the full configuration (including flowData, chatbotConfig, system prompts, and node configurations) of chatflows from Workspace B, Workspace C, and all other workspaces, as long as those chatflows have no API key assigned.

The controller at packages/server/src/controllers/chatflows/index.ts:90-107 validates the API key and calls the service:

The service at packages/server/src/services/chatflows/index.ts:223-245 builds the database query:

When keyonly is not provided as a query parameter (which is the default case), the query expands to include:

From FlowiseAI/Flowise's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
FlowiseServers and applications · github:flowiseai/flowise
  • Every version before 3.1.2

About Flowise

Build AI Agents, Visually

From its GitHub repository.
Archived
Yes, no longer maintainedGitHub
Weekly downloads (npm)
6,604npm, 15 Nov 2026
Docker Hub pulls
7,390,661Docker Hub, 15 Nov 2026
GitHub stars
55,573GitHub, 15 Nov 2026
Forks
25,094GitHub, 15 Nov 2026
Latest release
[email protected]GitHub, 15 Nov 2026
Released
29 Jul 2026GitHub
First published on GitHub
31 Mar 2023GitHub

References