Flowise versions before 3.1.0 contain logic errors in the secureAxiosRequest and secureFetch wrappers that were designed to block Server‑Side Request Forgery. These flaws allow a bypass of the allow/deny lists through DNS rebinding (a Time‑of‑Check Time‑of‑Use race) or by exploiting the default configuration, which does not enforce any deny list at all. The result is that an attacker can cause the Flowise application to issue arbitrary outbound HTTP or HTTPS requests to internal or external hosts, potentially exposing sensitive data or serving as a foothold for further attacks.

All releases of Flowise and flowise-components from FlowiseAI earlier than version 3.1.0 are affected. The vulnerability was fixed in the 3.1.0 release of both the application and its components.

The EPSS score of less than 1% indicates a very low current probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog. The CVSS score of 7.1 reflects a high impact on confidentiality and integrity because the flaw permits arbitrary outbound requests that could be used to enumerate internal services, exfiltrate data, or pivot to other systems. Based on the description, it is inferred that an attacker would need to reach the Flowise instance over its web interface to trigger the SSRF bypass; no explicit credential requirement is stated in the advisory.