CVE-2026-30823 in Flowise
Summary
by MITRE • 03/07/2026
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.0.13, there is an IDOR vulnerability, leading to account takeover and enterprise feature bypass via SSO configuration. This issue has been patched in version 3.0.13.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Analysis
by VulDB Data Team • 03/12/2026
The vulnerability identified as CVE-2026-30823 affects Flowise, a drag-and-drop interface for building customized large language model workflows. This application serves as a platform for creating and managing AI-powered conversational flows, making it a critical component in enterprise environments where sensitive data processing occurs. The vulnerability manifests as an Insecure Direct Object Reference flaw that allows unauthorized access to system resources through manipulated object references. This type of vulnerability falls under CWE-639, which specifically addresses authorization flaws where the application fails to properly validate object references, potentially allowing attackers to access resources they should not be permitted to access.
The technical implementation of this vulnerability stems from insufficient access control validation within the Single Sign-On configuration handling mechanisms of Flowise. Attackers can exploit this weakness by manipulating object references in API requests to access SSO configuration data belonging to other users or system administrators. This particular flaw enables attackers to bypass enterprise feature restrictions that should only be accessible to authorized personnel with appropriate privileges. The vulnerability specifically affects versions prior to 3.0.13, indicating that the developers identified and addressed the authorization gap in their patch release. The flaw allows for account takeover scenarios where malicious actors can assume the identity of legitimate users with elevated privileges, potentially gaining access to sensitive enterprise features and configuration settings.
The operational impact of this vulnerability extends beyond simple unauthorized access, as it creates a pathway for attackers to escalate privileges and gain control over critical system configurations. When combined with the SSO functionality, this vulnerability allows attackers to potentially compromise entire enterprise workflows by accessing and modifying authentication configurations. The attack surface is particularly concerning in environments where Flowise is used for sensitive data processing or where it serves as a central hub for AI-powered applications. Organizations using Flowise in production environments face significant risks including data exposure, unauthorized configuration changes, and potential lateral movement within their network infrastructure. The vulnerability can be exploited through standard web application attack vectors, making it particularly dangerous as it requires minimal specialized knowledge to execute successfully.
The mitigation strategy for this vulnerability involves immediate deployment of Flowise version 3.0.13 or later, which contains the necessary authorization controls to prevent object reference manipulation. Organizations should conduct comprehensive security assessments of their Flowise installations to identify any potential exploitation that may have occurred prior to patching. Security teams should implement additional monitoring for unusual SSO configuration access patterns and establish proper access control policies for administrative functions. This vulnerability aligns with ATT&CK technique T1078.004 which covers valid accounts through compromised credentials, and T1566.002 which addresses spearphishing through social engineering. The remediation process should include verification that all object references are properly validated against user permissions and that appropriate access controls are enforced at the application level. Additionally, organizations should review their overall application security posture to identify similar authorization gaps that may exist in other components of their AI infrastructure.