Insertion of Sensitive Information Into Sent Data Affecting flowise package, versions >=3.0.5 <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 applications- Snyk IDSNYK-JS-FLOWISE-16115550
- published21 Apr 2026
- disclosed17 Apr 2026
- creditDeathsPirate
Introduced: 17 Apr 2026
NewCVE-2026-41278 (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 Insertion of Sensitive Information Into Sent Data via the getSinglePublicChatflow handler in chatflows/index.ts. An attacker can retrieve sensitive flow configuration by requesting a public chatflow and reading the returned flowData payload. The exposed flowData can include node inputs and embedded credentials or authorization headers from the chatflow definition, allowing unauthenticated users to learn secrets used by the public flow.
Workarounds
- Disable public exposure for chatflows and chatbot configs so unauthenticated users cannot call
GET /api/v1/public-chatflows/:idor the public chatbot config endpoint and retrieve rawflowDatacontaining plaintext API keys, passwords, and credential IDs.