CVE-2026-56268 is a medium-severity incorrect authorization vulnerability in flowise (npm), affecting versions <= 3.1.1. It is fixed in 3.1.2.
Summary 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. Details 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: All chatflows bound to the provided API key (same workspace, expected behavior) ALL chatflows with apikeyid IS NULL (any workspace, no workspace filter) ALL chatflows with empty apikeyid (any workspace, no workspace filter) There is NO workspaceId filter in this query. The response includes the full ChatFlow entity, which contains: flowData - the complete workflow graph including system prompts, model names, internal URLs, custom code chatbotConfig - chatbot configuration including allowed origins apiConfig - API configuration and override settings textToSpeech / speechToText - TTS/STT configuration including credential IDs analytic - analytics configuration PoC Impact Cross-Workspace Information Disclosure: A user in any workspace can read the full configuration of chatflows from all other workspaces that do not have an API key assigned. This breaks workspace isolation. Intellectual Property Exposure: System prompts, custom function code, and workflow architecture of chatflows from other workspaces/organizations are exposed. Credential Reference Leakage: The textToSpeech and speechToText fields include credential IDs, which can be abused via the TTS generate endpoint. Amplified by Default: Most chatflows are created without an API key assigned (API keys are opt-in), so the majority of chatflows in a multi-workspace deployment are affected. Recommended Fix Add workspace scoping to the getChatflowByApiKey query by passing the API key workspace ID and filtering the OR clause:
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
npm
flowise (<= 3.1.1)flowise → 3.1.2 (npm)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-56268 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-56268 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-56268 in your environment →Upgrade flowise to 3.1.2 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-56268 is a medium-severity incorrect authorization vulnerability in flowise (npm), affecting versions <= 3.1.1. It is fixed in 3.1.2. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
flowise (npm) versions <= 3.1.1 is affected.
Yes. CVE-2026-56268 is fixed in 3.1.2. Upgrade to this version or later.
Whether CVE-2026-56268 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade flowise to 3.1.2 or later.