Server-side Request Forgery (SSRF) Affecting flowise package, versions <3.1.0
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-FLOWISE-16111571
- published20 Apr 2026
- disclosed16 Apr 2026
- creditSn1r
Introduced: 16 Apr 2026
NewCVE-2026-41270 (opens in a new tab)How to fix?
Upgrade flowise to version 3.1.0 or higher.
Overview
flowise is a Flowiseai Server
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) through the getHttpDenyList process in httpSecurity.ts. An attacker can reach internal or otherwise denied HTTP endpoints by supplying requests that rely on the HTTP deny list by using built-in modules such as http, https, or net. This leaves deployments exposed to server-side request forgery against services that operators expected to be blocked, allowing access to internal network resources and any data or actions those endpoints expose.