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's Flowise product versions prior to 3. 1. 0. The GET /api/v1/public-chatflows/:id endpoint returns the full chatflow object without sanitization, exposing sensitive information such as credential IDs, plaintext API keys, and password-type fields. The issue is exacerbated in the released v3. 0. 13 Docker image, which lacks the sanitization function entirely, leading to raw sensitive data exposure. This vulnerability is fixed in version 3. 1. 0.
AI Analysis
Technical Summary
FlowiseAI Flowise versions before 3.1.0 have an information exposure vulnerability (CWE-200) where the API endpoint GET /api/v1/public-chatflows/:id returns unsanitized chatflow data for public chatflows. The data includes sensitive fields like credential IDs, plaintext API keys, and passwords. The sanitization function intended to prevent this exposure is missing in the v3.0.13 Docker image, resulting in complete raw flow data disclosure. The vulnerability has a CVSS 4.0 score of 8.7, indicating high severity. The issue is resolved in Flowise version 3.1.0.
Potential Impact
Unauthorized actors can access sensitive information including credential identifiers, plaintext API keys, and password-type fields through the vulnerable API endpoint. This exposure can lead to compromise of credentials and unauthorized access to systems relying on these secrets. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade Flowise to version 3.1.0 or later, where this vulnerability is fixed. Since the vulnerability is resolved in 3.1.0, applying this official fix is the recommended remediation. No other mitigations are specified or required.
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's Flowise product versions prior to 3. 1. 0. The GET /api/v1/public-chatflows/:id endpoint returns the full chatflow object without sanitization, exposing sensitive information such as credential IDs, plaintext API keys, and password-type fields. The issue is exacerbated in the released v3. 0. 13 Docker image, which lacks the sanitization function entirely, leading to raw sensitive data exposure. This vulnerability is fixed in version 3. 1. 0.
CVSS v4.0
Score 8.7high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
FlowiseAI Flowise versions before 3.1.0 have an information exposure vulnerability (CWE-200) where the API endpoint GET /api/v1/public-chatflows/:id returns unsanitized chatflow data for public chatflows. The data includes sensitive fields like credential IDs, plaintext API keys, and passwords. The sanitization function intended to prevent this exposure is missing in the v3.0.13 Docker image, resulting in complete raw flow data disclosure. The vulnerability has a CVSS 4.0 score of 8.7, indicating high severity. The issue is resolved in Flowise version 3.1.0.
Potential Impact
Unauthorized actors can access sensitive information including credential identifiers, plaintext API keys, and password-type fields through the vulnerable API endpoint. This exposure can lead to compromise of credentials and unauthorized access to systems relying on these secrets. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade Flowise to version 3.1.0 or later, where this vulnerability is fixed. Since the vulnerability is resolved in 3.1.0, applying this official fix is the recommended remediation. No other mitigations are specified or required.
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: 5/1/2026, 8:49:24 PM
Last updated: 6/7/2026, 8:04:31 AM
Views: 52
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.