A Server-Side Request Forgery vulnerability in Flowise allows authenticated users to bypass security controls and access sensitive internal network resources.

This flaw involves an improper access control issue where the NodeVM sandbox permits the use of Node.js modules like http, https, and net, which bypass established SSRF protections. The vulnerability is exploitable by any authenticated user with access to the Custom Function feature.

The ability for an attacker to perform SSRF requests poses a significant risk to internal infrastructure. By reaching internal-only services, such as cloud provider metadata endpoints or internal APIs, an attacker could potentially exfiltrate sensitive configuration data, credentials, or internal network topology information. Given the CVSS score of 7.1, this is classified as a High severity issue that requires immediate attention to prevent lateral movement within the network.

Immediate Action: Update both Flowise and flowise-components to version 3.1.0 or later to apply the necessary sandbox restrictions.

Proactive Monitoring: Review application and server logs for unusual outbound network requests originating from the Flowise instance, particularly those targeting internal IP addresses or cloud metadata services.

Compensating Controls: If immediate patching is not feasible, restrict network access for the Flowise server to only essential external services, effectively isolating it from sensitive internal segments.

Public Exploit Available: No confirmed public exploit (weaponized or published PoC) exists in the provided data.

This vulnerability represents a high-risk security gap that can be leveraged to compromise internal systems through the Flowise interface. Organizations should prioritize upgrading to version 3.1.0 immediately to eliminate the bypass mechanism. Failure to remediate this issue leaves the environment vulnerable to unauthorized internal network reconnaissance and potential data exfiltration.