CVE-2026-41278: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in FlowiseAI Flowise
CVE-2026-41278 is a high-severity vulnerability in FlowiseAI Flowise versions prior to 3. 1. 0 where the GET /api/v1/public-chatflows/:id endpoint exposes sensitive information without sanitization. Specifically, the API returns raw flow data including credential IDs, plaintext API keys, and password-type fields. The vulnerability was found to be worse than initially assessed because the sanitization function does not exist in the released v3. 0. 13 Docker image. This issue is fixed in version 3. 1. 0.
AI Analysis
Technical Summary
FlowiseAI Flowise, a drag & drop interface for building customized large language model flows, has a vulnerability (CVE-2026-41278) affecting versions before 3.1.0. The GET /api/v1/public-chatflows/:id endpoint returns the full chatflow object without sanitizing sensitive fields for public chatflows. Analysis of the v3.0.13 Docker image revealed the absence of the sanitizeFlowDataForPublicEndpoint function, resulting in exposure of raw flowData including credential IDs, plaintext API keys, and password-type fields. This constitutes an exposure of sensitive information (CWE-200). The vulnerability is addressed in version 3.1.0.
Potential Impact
Exploitation of this vulnerability allows unauthorized actors to retrieve sensitive information such as credential IDs, plaintext API keys, and passwords from public chatflows via the API endpoint. This exposure can lead to unauthorized access to systems or services that rely on these credentials. The CVSS 4.0 base score is 8.7 (high severity), indicating a significant risk due to network accessibility, no required privileges or user interaction, and high impact on confidentiality.
Mitigation Recommendations
This vulnerability is fixed in Flowise version 3.1.0. Users should upgrade to version 3.1.0 or later to remediate the issue. Since the vulnerability affects self-hosted instances (not a cloud service), patching the software is required. Patch status is not explicitly stated beyond the fix in 3.1.0, so users should verify the upgrade and consult vendor advisories for any additional guidance.
CVE-2026-41278: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in FlowiseAI Flowise
Description
CVE-2026-41278 is a high-severity vulnerability in FlowiseAI Flowise versions prior to 3. 1. 0 where the GET /api/v1/public-chatflows/:id endpoint exposes sensitive information without sanitization. Specifically, the API returns raw flow data including credential IDs, plaintext API keys, and password-type fields. The vulnerability was found to be worse than initially assessed because the sanitization function does not exist in the released v3. 0. 13 Docker image. This issue is fixed in version 3. 1. 0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
FlowiseAI Flowise, a drag & drop interface for building customized large language model flows, has a vulnerability (CVE-2026-41278) affecting versions before 3.1.0. The GET /api/v1/public-chatflows/:id endpoint returns the full chatflow object without sanitizing sensitive fields for public chatflows. Analysis of the v3.0.13 Docker image revealed the absence of the sanitizeFlowDataForPublicEndpoint function, resulting in exposure of raw flowData including credential IDs, plaintext API keys, and password-type fields. This constitutes an exposure of sensitive information (CWE-200). The vulnerability is addressed in version 3.1.0.
Potential Impact
Exploitation of this vulnerability allows unauthorized actors to retrieve sensitive information such as credential IDs, plaintext API keys, and passwords from public chatflows via the API endpoint. This exposure can lead to unauthorized access to systems or services that rely on these credentials. The CVSS 4.0 base score is 8.7 (high severity), indicating a significant risk due to network accessibility, no required privileges or user interaction, and high impact on confidentiality.
Mitigation Recommendations
This vulnerability is fixed in Flowise version 3.1.0. Users should upgrade to version 3.1.0 or later to remediate the issue. Since the vulnerability affects self-hosted instances (not a cloud service), patching the software is required. Patch status is not explicitly stated beyond the fix in 3.1.0, so users should verify the upgrade and consult vendor advisories for any additional guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-18T14:01:46.802Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69ea9e7887115cfb686fc398
Added to database: 4/23/2026, 10:34:32 PM
Last enriched: 4/23/2026, 11:21:51 PM
Last updated: 4/24/2026, 6:09:11 AM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.