Flowise: APIChain Prompt Injection SSRF in GET/POST API Chains

published 2026-04-16 6 mo ago modified 2026-10-26 13 d ago also GHSA-6r77-hqx7-7vw8 , EUVD-2026-25288

cvss: 7.1; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 14%
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, a Server-Side Request Forgery (SSRF) vulnerability exists in FlowiseAI's POST/GET API Chain components that allows unauthenticated attackers to force the server to make arbitrary HTTP requests to internal and external systems. By injecting malicious prompt templates, attackers can bypass the intended API documentation constraints and redirect requests to sensitive internal services, potentially leading to internal network reconnaissance and data exfiltration. 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.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-6r77-hqx7-7vw8 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.0	7.1	CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
NVD	3.1	8.3	CVSS:3.1/AV:N/AC:L/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

References

github.com /FlowiseAI/Flowise/security/advisories/GHSA-6r77-hqx7-7vw8
exploit, web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2026-41271
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