Flowise: SSRF Protection Bypass (TOCTOU & Default Insecure)

published 2026-04-16 6 mo ago modified 2026-10-26 13 d ago also GHSA-2x8m-83vc-6wv4 , EUVD-2026-25289

cvss: 7.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits: 0; none known

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, the core security wrappers (secureAxiosRequest and secureFetch) intended to prevent Server-Side Request Forgery (SSRF) contain multiple logic flaws. These flaws allow attackers to bypass the allow/deny lists via DNS Rebinding (Time-of-Check Time-of-Use) or by exploiting the default configuration which fails to enforce any deny list. This vulnerability is fixed in 3.1.0.

Patch / fix

fixed in 3

npm flowise 3.1.0
npm flowise-components 3.1.0
flowiseai flowise 3.1.0

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: total
Assessed: 6 mo ago (2026-04-23)

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-2x8m-83vc-6wv4 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.1	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
GitHub	3.0	7.1	CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L

Affected packages

ecosystem	package	affected	fixed in
npm	flowise	<3.1.0	3.1.0
npm	flowise-components	<3.1.0	3.1.0

Affected products

FlowiseAI Flowise
FlowiseAI flowise-components

Classification

Weakness

CWE-918 Server-Side Request Forgery
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition

References

github.com /FlowiseAI/Flowise/security/advisories/GHSA-2x8m-83vc-6wv4
exploit, web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2026-41272
advisory
github.com /FlowiseAI/Flowise
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary