Server-side Request Forgery (SSRF) Affecting flowise-components 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-FLOWISECOMPONENTS-16109634
- published19 Apr 2026
- disclosed16 Apr 2026
- creditESPanda666
Introduced: 16 Apr 2026
NewCVE-2026-41272 (opens in a new tab)How to fix?
Upgrade flowise-components to version 3.1.0 or higher.
Overview
flowise-components is a Flowiseai Components
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the secureAxiosRequest and secureFetch functions. An attacker can gain unauthorized access to internal services and potentially exfiltrate sensitive data or manipulate internal resources by bypassing allow/deny list protections through DNS rebinding or exploiting insecure default configurations. This is only exploitable if the environment variable HTTP_DENY_LIST is unset or misconfigured.