Is CVE-2026-41270 exploited in the wild?

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

How severe is CVE-2026-41270?

High severity, with a CVSS score of 7.1, published 23 April 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-41270?

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-41270 attacked?

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

Am I affected by CVE-2026-41270?

Check whether you run FlowiseAI Flowise, 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-41270: Flowise: SSRF Protection Bypass via Unprotected Built-in HTTP Modules in Custom Function Sandbox

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-41270?

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-41270 attacked?

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

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

Check whether you run FlowiseAI Flowise, 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-41270 · Severity: high · CVSS 7.1 · Published 2026-04-23

Flowise is a low-code platform for building AI applications that includes a custom function feature allowing authenticated users to write JavaScript code. An attacker with valid API credentials can bypass the intended SSRF (Server-Side Request Forgery) protection controls and make arbitrary HTTP requests to internal networks, cloud metadata services, and other sensitive endpoints—potentially stealing AWS IAM credentials or accessing internal databases and administrative panels.

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

Quick answers

Is CVE-2026-41270 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41270 being exploited in the wild.
How severe is CVE-2026-41270?: High severity, with a CVSS score of 7.1, published 23 April 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-41270?: 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-41270 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-41270?: Check whether you run FlowiseAI Flowise, 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

The vulnerability is an SSRF protection bypass in the Custom Function sandbox implementation. While Flowise protects against SSRF by wrapping axios and node-fetch with an HTTP_DENY_LIST check, the sandbox configuration (packages/components/src/utils.ts, line 56) allows unrestricted access to Node.js built-in modules including http, https, net, dns, and dgram. An authenticated attacker can require() these modules directly and make arbitrary HTTP/DNS requests that circumvent the intended deny-list policy. The attack requires valid API credentials or an authenticated session, and the impact is severe: attackers can steal temporary cloud credentials from metadata services (e.g., AWS IMDSv2), enumerate internal network topology, and access databases or admin panels. Patches are available in Flowise 3.1.0 and flowise-components 3.1.0; versions 3.0.13 and earlier are affected.

Affected products

FlowiseAI Flowise ≤ 3.0.13
FlowiseAI flowise-components ≤ 3.0.13

Identifiers

CVE-2026-41270
GHSA-xhmj-rg95-44hv

Timeline

2026-04-16: disclosed: Published on GitHub Security Advisory
2026-04-16: patched: Patched in Flowise 3.1.0 and flowise-components 3.1.0

References

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-xhmj-rg95-44hv

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