An SSRF vulnerability in Flowise allows authenticated attackers to abuse the fetch links endpoint to perform unauthorized outbound requests.

This vulnerability is a Server-Side Request Forgery (CWE-918) caused by an incomplete deny-list in the fetch links endpoint. The attack requires low-level authentication to execute.

The CVSS score of 7.7 reflects the high potential for SSRF to be used to scan internal networks, access metadata services, or interact with internal APIs that are otherwise unreachable from the public internet. This can lead to significant data exposure and further escalation of privileges within the internal infrastructure.

Immediate Action: Review the Flowise vendor advisory for specific mitigation steps, as the product has reached a sunset phase.

Proactive Monitoring: Monitor outbound network traffic from the Flowise server for unusual connections to internal network segments or unauthorized external endpoints.

Compensating Controls: Implement strict egress filtering on the host machine to prevent the application from making unauthorized requests to internal resources or sensitive metadata services.

Public Exploit Available: Yes, a public Proof-of-Concept is available via GitHub.

Given that Flowise has reached the end of its lifecycle, users should evaluate the necessity of the software and migrate to a supported alternative. If the software must remain in production, aggressive network-level egress filtering is required to mitigate the risk of SSRF exploitation.