CVE-2026-30820 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, Flowise trusts any HTTP client that sets the header x-request-from: internal, allowing an authenticated tenant session to bypass all /api/v1/** authorization checks. With only a browser cookie, a low-privilege tenant can invoke internal administration endpoints (API key management, credential stores, custom function execution, etc.), effectively escalating privilege. This issue has been patched in version 3.0.13.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 03/12/2026
The vulnerability identified as CVE-2026-30820 affects Flowise, a drag and drop interface for building customized large language model flows that has been widely adopted for enterprise AI deployment. This authentication bypass flaw stems from improper validation of the x-request-from: internal header, which Flowise incorrectly interprets as sufficient authorization for accessing internal administrative endpoints. The vulnerability exists in versions prior to 3.0.13 and represents a critical security oversight that fundamentally undermines the application's access control mechanisms. Organizations using Flowise in production environments may be at risk of unauthorized privilege escalation if they have not updated to the patched version.
The technical flaw manifests through a trust-based misconfiguration where Flowise accepts any HTTP client that presents the x-request-from: internal header without proper verification of the client's actual authorization status. This header-based trust model creates a dangerous attack vector where a low-privilege tenant user can simply manipulate HTTP headers to gain access to sensitive administrative functions. The vulnerability specifically affects all endpoints under the /api/v1/** path, which includes critical administrative operations such as API key management, credential store access, and custom function execution capabilities. The flaw essentially allows an attacker to bypass all authorization checks by simply crafting a request with the appropriate header value, even when the user lacks legitimate administrative privileges.
The operational impact of this vulnerability is severe and multifaceted, as it enables a low-privilege tenant user to effectively escalate their privileges to administrative level access. This privilege escalation allows unauthorized users to manage API keys, access sensitive credential stores, and execute arbitrary code through custom functions, potentially leading to complete system compromise. The attack requires only a valid browser cookie from an authenticated tenant session, making it particularly dangerous as it can be exploited through standard web browser interactions without requiring additional authentication credentials or specialized tools. The vulnerability essentially provides a backdoor into the administrative functions of Flowise that could be exploited by malicious actors within the organization or external attackers who have gained access to a tenant account.
Organizations should immediately update to Flowise version 3.0.13 or later to remediate this vulnerability, as the patch addresses the header validation issue by implementing proper authorization checks that verify the actual user's privileges before granting access to administrative endpoints. Security teams should conduct immediate assessments of their Flowise deployments to ensure all instances have been updated and monitor for any suspicious activities that might indicate exploitation attempts. The vulnerability aligns with CWE-284 (Improper Access Control) and represents a classic case of insecure direct object reference where the application trusts client-provided headers without proper verification. From an ATT&CK perspective, this vulnerability maps to privilege escalation techniques and could enable adversaries to move laterally within affected systems by leveraging administrative capabilities. Organizations should also implement additional monitoring of API access patterns and header values to detect potential exploitation attempts, as the vulnerability could be used in combination with other attack vectors to achieve more extensive system compromise.