CVE-2026-67622: Authorization Bypass Through User-Controlled Key in FlowiseAI Flowise
Flowise through 3.1.4 contains an insecure direct object reference vulnerability in the OpenAI Assistants integration that allows authenticated attackers to access credentials belonging to other workspaces by supplying an arbitrary credential UUID to Assistants endpoints without workspace ownership verification. Attackers can enumerate cross-workspace assistant metadata, retrieve file and vector store listings, and upload files into victim workspaces by exploiting the missing workspace-scoped authorization check in the credential lookup logic.
AI Analysis
Technical Summary
CVE-2026-67622 is an authorization bypass vulnerability in Flowise through version 3.1.4. The vulnerability exists in the OpenAI Assistants integration where the application fails to verify workspace ownership when processing credential UUIDs. Authenticated attackers can exploit this missing workspace-scoped authorization check to access credentials belonging to other workspaces, enumerate assistant metadata across workspaces, retrieve file and vector store listings, and upload files into victim workspaces. This is classified as CWE-639 (Authorization Bypass Through User-Controlled Key).
Potential Impact
An attacker with authenticated access can access sensitive credentials from other workspaces, potentially leading to unauthorized data exposure. They can also enumerate metadata and file listings across workspaces and upload files into victim workspaces, which may lead to further compromise or data manipulation. The vulnerability has a high severity with a CVSS 4.0 score of 8.5, indicating significant impact if exploited.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict authenticated user permissions to the minimum necessary and monitor for suspicious activity related to credential UUID usage. Avoid sharing credential UUIDs and consider additional access controls at the application layer.
CVE-2026-67622: Authorization Bypass Through User-Controlled Key in FlowiseAI Flowise
Description
Flowise through 3.1.4 contains an insecure direct object reference vulnerability in the OpenAI Assistants integration that allows authenticated attackers to access credentials belonging to other workspaces by supplying an arbitrary credential UUID to Assistants endpoints without workspace ownership verification. Attackers can enumerate cross-workspace assistant metadata, retrieve file and vector store listings, and upload files into victim workspaces by exploiting the missing workspace-scoped authorization check in the credential lookup logic.
CVSS v4.0
Score 8.5high
Affected software
FlowiseAI
Flowise
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-67622 is an authorization bypass vulnerability in Flowise through version 3.1.4. The vulnerability exists in the OpenAI Assistants integration where the application fails to verify workspace ownership when processing credential UUIDs. Authenticated attackers can exploit this missing workspace-scoped authorization check to access credentials belonging to other workspaces, enumerate assistant metadata across workspaces, retrieve file and vector store listings, and upload files into victim workspaces. This is classified as CWE-639 (Authorization Bypass Through User-Controlled Key).
Potential Impact
An attacker with authenticated access can access sensitive credentials from other workspaces, potentially leading to unauthorized data exposure. They can also enumerate metadata and file listings across workspaces and upload files into victim workspaces, which may lead to further compromise or data manipulation. The vulnerability has a high severity with a CVSS 4.0 score of 8.5, indicating significant impact if exploited.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict authenticated user permissions to the minimum necessary and monitor for suspicious activity related to credential UUID usage. Avoid sharing credential UUIDs and consider additional access controls at the application layer.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-29T21:07:39.204Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a75070abf8831d5395f5c12
Added to database: 08/06/2026, 22:13:30 UTC
Last enriched: 08/14/2026, 16:07:16 UTC
Last updated: 09/21/2026, 22:01:36 UTC
Views: 50
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.