Is CVE-2026-56275 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-56275 being exploited in the wild.

How severe is CVE-2026-56275?

High severity, with a CVSS score of 7.1, published 23 June 2026.

Which products and versions are affected?

flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0; flowise-components (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.

Is there a fix for CVE-2026-56275?

Yes. flowise (npm): upgrade to 3.1.0 or later; flowise-components (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 CVE-2026-56275 attacked?

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

Am I affected by CVE-2026-56275?

Check whether you run flowise (npm) or flowise-components (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.

CVE-2026-56275: Flowise SSRF in Execute Flow node

Q: Which products and versions are affected?

flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0; flowise-components (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.

Q: Is there a fix for CVE-2026-56275?

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

Q: How is CVE-2026-56275 attacked?

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

Q: Am I affected by CVE-2026-56275?

Check whether you run flowise (npm) or flowise-components (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.

CVE-2026-56275 · Severity: high · CVSS 7.1 · Published 2026-06-23

Flowise is an open-source tool used to build customized AI workflows and LLM applications. A security flaw in the 'Execute Flow' component allows users with low-level access to force the server to make unauthorized requests to internal systems. This could allow an attacker to scan your private network, access sensitive cloud metadata, or interact with internal services that are not supposed to be exposed to the internet.

Technologies: flowise (npm), flowise-components (npm). Vendors: npm.

Quick answers

Is CVE-2026-56275 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-56275 being exploited in the wild.
How severe is CVE-2026-56275?: High severity, with a CVSS score of 7.1, published 23 June 2026.
Which products and versions are affected?: flowise (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0; flowise-components (npm) <= 3.0.13, SEMVER:introduced=0,fixed=3.1.0.
Is there a fix for CVE-2026-56275?: Yes. flowise (npm): upgrade to 3.1.0 or later; flowise-components (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 CVE-2026-56275 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-56275?: Check whether you run flowise (npm) or flowise-components (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
```
flowise-components (npm): upgrade to 3.1.0 or later
```
npm install flowise-components@3.1.0
```

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in Flowise versions prior to 3.1.0 within the 'Execute Flow' node. The vulnerability stems from a failure to invoke 'secureFetch' verification in the 'httpSecurity.ts' component when processing the base URL field. An authenticated attacker with low privileges can provide intranet or loopback addresses to bypass intended security denylists. This allows the attacker to initiate HTTP requests from the server to internal network addresses, potentially leading to the enumeration of internal services, access to cloud instance metadata (IMDS), or unauthorized interaction with internal APIs. The issue is resolved in version 3.1.0 by implementing proper validation via secureFetch.

Affected products

FlowiseAI Flowise < 3.1.0
FlowiseAI flowise-components < 3.1.0

Identifiers

CVE-2026-56275
GHSA-9hrv-gvrv-6gf2

Timeline

2026-04-15: advisory: GitHub Security Advisory published
2026-06-23: disclosed: NVD publication date

References

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