Flowise: Six Auth and AuthZ Flaws Disclosed Together, Patched in v3.1.5
Six vulnerabilities in Flowise, including authentication bypass and authorization flaws, were disclosed on September 26, 2026, patched in v3.1.5.
Key findings
- Six vulnerabilities disclosed in Flowise on September 26, 2026, patched in v3.1.5.
- Multiple authentication bypass flaws allow unauthorized account access via SSO and email.
- Authorization issues enable unauthorized access to chat history and upsert data.
- Credential lookup flaws risk exposure of sensitive user credentials.
- BullMQ admin dashboard vulnerable under specific configurations.
On September 26, 2026, a batch of six vulnerabilities was disclosed in Flowise, an open-source low-code tool for building LLM applications. The vulnerabilities, all patched in version 3.1.5, span several critical areas including authentication bypass, authorization flaws, and information exposure, with several rated as High severity. These issues collectively pose a significant risk to users running vulnerable instances of Flowise.
Several vulnerabilities revolve around inadequate access controls and authorization checks. CVE-2026-100610 highlights missing route-level permission checks on GET /api/v1/upsert-history/:id and PATCH /api/v1/upsert-history endpoints, allowing unauthorized access to and modification of upsert history data based solely on a provided chatflowid. Similarly, CVE-2026-100605 points to missing route-level RBAC checks on chat message endpoints, enabling low-privileged API keys to read and delete chat history.
Authentication bypass is another major theme within this disclosure. CVE-2026-100607 describes a critical flaw where Flowise resolves SSO and local-password users solely by email. This allows attackers to claim any email address at an SSO provider and authenticate as any existing user, gaining complete account access. Complementing this, CVE-2026-100606 details an authentication bypass in the SSO login path for enterprise/platform modes. When an SSO callback matches an invited user's email, the system copies the user record, including sensitive single-use tokens, potentially leading to account takeover.
Further weaknesses include improper credential handling and dashboard security. CVE-2026-100609 reveals that Flowise looks up credentials by ID without filtering on the requesting user's workspace, leading to potential exposure of sensitive credentials. Additionally, CVE-2026-100608 addresses a lack of authorization enforcement on the BullMQ admin dashboard when specific configurations are met, making the queue management interface accessible via a middleware that only verifies a token.
The disclosed vulnerabilities affect Flowise versions up to 3.1.4. All identified issues have been addressed in version 3.1.5, which users are strongly urged to upgrade to. The broad impact of these vulnerabilities, ranging from unauthorized data access to complete account takeover, underscores the importance of timely patching and secure configuration for Flowise deployments. Users should review their current versions and apply the available update to mitigate these risks.
The batch of vulnerabilities disclosed on September 26, 2026, highlights critical security weaknesses in Flowise, particularly concerning authentication and authorization mechanisms. The coordinated disclosure of these six CVEs, all patched in version 3.1.5, provides a clear roadmap for users to secure their deployments. The severity of these flaws, with multiple High-rated issues, necessitates immediate attention from administrators to prevent potential exploitation and data breaches.
Key areas of concern include:
- Authentication Bypass: Flaws in SSO and email-based authentication allow attackers to impersonate users and gain unauthorized access.
- Authorization Flaws: Missing access controls on API endpoints and the BullMQ dashboard enable unauthorized data access and manipulation.
- Credential Exposure: Vulnerabilities in credential lookup mechanisms risk exposing sensitive user credentials.
Administrators are advised to update to Flowise version 3.1.5 or later to address these security concerns.
CVEs addressed in this disclosure include CVE-2026-100610, CVE-2026-100609, CVE-2026-100608, CVE-2026-100607, CVE-2026-100606, and CVE-2026-100605.