Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Low severity, with a CVSS score of 3.1, published 23 June 2026.

Which products and versions are affected?

flowise (npm) SEMVER:introduced=0,fixed=3.1.0.

Is there a fix for This vulnerability?

Yes. flowise (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network, in a software library.

Check whether you run flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Flowise Execute Flow SSRF in base URL configuration

Severity: low · CVSS 3.1 · Published 2026-06-23

Flowise is an open-source low-code workflow automation platform. A server-side request forgery (SSRF) vulnerability in the Execute Flow node allows authenticated attackers to bypass security checks and make HTTP requests to internal network addresses, cloud metadata services, or other restricted resources by manipulating the base URL field. This could enable attackers to discover internal services, access sensitive management interfaces, and leak confidential configuration or credentials.

Technologies: flowise (npm). Vendors: npm.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Low severity, with a CVSS score of 3.1, published 23 June 2026.
Which products and versions are affected?: flowise (npm) SEMVER:introduced=0,fixed=3.1.0.
Is there a fix for This vulnerability?: Yes. flowise (npm): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a software library.
Am I affected?: Check whether you run flowise (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

flowise (npm): upgrade to 3.1.0 or later
```
npm install flowise@3.1.0
```

Technical details

The Execute Flow node in Flowise before 3.1.0 contains a server-side request forgery (CWE-918) vulnerability in httpSecurity.ts. The vulnerable component fails to call the secureFetch verification function when processing intranet addresses provided through the base URL field, bypassing the checkDenyList and resolveAndValidate security checks. Exploitation requires authentication (API key or bearer token), network access to the Flowise API endpoint, and the ability to configure or trigger an Execute Flow node with a malicious base URL. A successful attack enables arbitrary HTTP requests from the server to internal networks, cloud metadata endpoints, or internal services for reconnaissance and lateral movement. The vulnerability was fixed in version 3.1.0.

Affected products

Flowise Flowise < 3.1.0

Timeline

2026-06-23: disclosed: Original advisory published (GHSA-w4hm-rrxg-pxcf)
2026: patched: Fixed in version 3.1.0
2026-09-23: other: Advisory withdrawn as duplicate of GHSA-9hrv-gvrv-6gf2

References

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-9hrv-gvrv-6gf2

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.