CVE-2026-91933
Received Received - Intake

Flowise 3.1.4 Workspace Authorization Bypass via ChatFlowID

Publication date: 2026-09-15

Last updated on: 2026-09-15

Assigner: VulnCheck

Description
Flowise before 3.1.4 fails to enforce workspace-level authorization checks in openai-realtime endpoints, allowing authenticated users to access tools from ChatFlows in other workspaces by supplying an unscoped chatflowid. Attackers can invoke GET and POST requests to retrieve tool definitions and execute tools from victim workspaces, triggering external side effects and accessing sensitive tool outputs.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-15
Last Modified
2026-09-15
Generated
2026-09-15
AI Q&A
2026-09-15
EPSS Evaluated
N/A
NVD
CVE-2026-91933
EUVD
EUVD-2026-78791

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
flowise flowise to 3.1.4 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Flowise before version 3.1.4 has a flaw where authenticated users can bypass workspace-level authorization checks in openai-realtime endpoints. By providing an unscoped chatflowid, they can access tools from ChatFlows in other workspaces. This allows sending GET and POST requests to retrieve tool definitions and execute tools from victim workspaces, potentially causing side effects and accessing sensitive outputs.

Detection Guidance

To detect this vulnerability, monitor network traffic for unauthorized GET or POST requests to Flowise's /api/v1/openai-realtime/:id endpoints. Check logs for requests using unscoped chatflow IDs across different workspaces. Verify if users can access tools or outputs from workspaces they do not belong to.

Impact Analysis

An attacker with access to one workspace could access tools and data in other workspaces, leading to unauthorized tool execution, retrieval of sensitive outputs, and potential side effects on external integrations. This could result in data breaches, unauthorized actions, or disruption of services.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. It may result in data breaches, unauthorized processing, or disclosure of protected health information, potentially leading to legal penalties and compliance failures.

Mitigation Strategies

Immediately upgrade Flowise to version 3.1.4 or later to patch the authorization bypass. Ensure all endpoints enforce workspace-level authorization checks. Review and restrict access to /api/v1/openai-realtime/:id endpoints. Audit logs for suspicious cross-workspace tool access attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-91933. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart