GitHub Advisoryadvisory · npm
GHSA-9hrv-gvrv-6gf2 Flowise Execute Flow function has an SSRF vulnerability
MEDIUM
Official page ↗
- Aliases
- CVE-2026-56275
- Ecosystem
- npm
- Packages
- flowise, flowise-components
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
- Weaknesses
- CWE-918
- Reviewed
- 2026-04-16
Affected packages
• npm flowise: < 3.1.0 → fixed in 3.1.0
• npm flowise-components: < 3.1.0 → fixed in 3.1.0
Description
Summary
The attacker provides an intranet address through the base url field configured in the Execute Flow node
→ Bypass checkDenyList / resolveAndValidate in httpSecurity.ts (not called)
→ Causes the server to initiate an HTTP request to any internal network address, read cloud metadata, or detect internal network services
Details
Then initiate the call:
```
POST /api/v1/prediction/d6739838-d3b3-43d9-86ff-911a3d757a7e HTTP/1.1
Host: 127.0.0.1:3000
Content-Type: application/json
Authorization: Bearer apikey
Content-Length: 17
{"question": "1"}
```
Server received a request:
And there is an echo:
Fix:
Call secureFetch for verification
Impact
This is a Server-Side Request Forgery (SSRF) vulnerability that may lead to the following risks:
• Explore Internal Web Applications
• Access sensitive management interfaces
• Leak internal configuration, credentials, or confidential information
This vulnerability significantly increases the risk of internal service enumeration and potential lateral movement in enterprise environments.
Related
Alias · CVE (1)
- CVE-2026-56275 Flowise before 3.1.0 contains a server-side request forgery vulnerability in the Execute Flow node that allows attackers to bypass security… vulnerability
Weakness · CWE (1)
- CWE-918 Server-Side Request Forgery weakness