Flowise versions prior to 3.1.0 are susceptible to Server-Side Request Forgery, which may allow authenticated attackers to bypass security controls and interact with internal network resources.

The application fails to properly validate requests within its core security wrappers (secureAxiosRequest and secureFetch), enabling SSRF attacks. An authenticated attacker can exploit these logic flaws to bypass intended allow or deny lists, potentially accessing sensitive internal services.

Successful exploitation of this SSRF vulnerability allows an attacker to interact with internal systems that are not exposed to the public internet. This can lead to the unauthorized disclosure of internal data, interaction with internal APIs, or the circumvention of network segmentation. Given the CVSS score of 7.1, this represents a high-risk security flaw that could facilitate deeper lateral movement within the network infrastructure.

Immediate Action: Update both the Flowise and flowise-components packages to version 3.1.0 or later to implement the corrected request filtering logic.

Proactive Monitoring: Review application logs for suspicious outbound requests originating from the Flowise service, particularly those targeting internal IP addresses or local loopback interfaces.

Compensating Controls: Implement strict egress filtering on the host machine running Flowise to prevent the application from initiating unauthorized network connections to internal infrastructure.

Public Exploit Available: No confirmed public exploit (weaponized or otherwise) is currently available in the provided data.

Organizations utilizing Flowise must prioritize the update to version 3.1.0 to resolve the identified logic flaws in the security wrappers. Because this vulnerability facilitates SSRF, failing to patch may expose internal services to unauthorized access. Apply the update immediately to ensure the integrity of your internal network environment.