CVE-2026-41278: Flowise Public Chatflow Endpoints Return Unsanitized Vulnerability

HIGH
Advisory Identifier: GHSA-w47f-j8rh-wx87
CVSS 7.5
CWE-200
Published
Advisory Summary

CVE-2026-41278 is a HIGH (CVSS 7.5) public chatflow endpoints return unsanitized vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Flowise libraries in the npm ecosystem. The issue involves public chatflow endpoints return unsanitized flowdata including plaintext api keys, passwords, and credential ids. Remediation is available by upgrading affected packages to version 3.1.0.

CVE-2026-41278 at a Glance

CVE Identifier CVE-2026-41278
GHSA Identifier GHSA-w47f-j8rh-wx87
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Flowise
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-41278

To remediate this vulnerability, upgrade all affected Flowise dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

flowise fixed: 3.1.0
npm install flowise@3.1.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls flowise

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-41278, inspect your project dependencies using npm:

npm ls flowise

Analyze the terminal output to locate any version of Flowise in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.1.0), your application is affected.

Note: The npm ls flowise command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Flowise, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The `GET /api/v1/public-chatflows/:id` endpoint returns the full chatflow object **without sanitization** for public chatflows. Docker validation revealed this is worse than initially assessed: the `sanitizeFlowDataForPublicEndpoint` function does NOT exist in the released v3.0.13 Docker image. Both `public-chatflows` AND `public-chatbotConfig` return completely raw flowData including credential IDs, plaintext API keys, and password-type fields. ### Root Cause ```typescript // packages/server/src/controllers/chatflows/index.ts:218-220 const chatflow = await chatflowsService.getChatflowById(req.params.id) if (!chatflow) return res.status(StatusCodes.NOT_FOUND).json(...) if (chatflow.isPublic) return res.status(StatusCodes.OK).json(chatflow) // ← NO sanitization! ``` ### Docker Validation (v3.0.13) Created public chatflow with credential IDs and passwords in flowData: ```json { "flowData": "{\"nodes\":[{\"data\":{\"credential\":\"e92a39bf-...\",\"inputs\":{\"password\":\"sk-supersecretkey123\",\"apiKey\":\"should-not-leak\"}}}]}" } ``` The `sanitizeFlowDataForPublicEndpoint` function only exists in unreleased HEAD, and even there, only `public-chatbotConfig` calls it — `public-chatflows` never does. ### Impact - **Credential IDs** leaked — enables OAuth2 token theft chain (Finding 1) - **Plaintext API keys and passwords** leaked — direct third-party account compromise - **Node configurations** leaked — reveals internal architecture and endpoint URLs - Both `public-chatflows` and `public-chatbotConfig` are affected in the released version ### Suggested Fix Apply sanitization to both public endpoints: ```typescript const sanitized = sanitizeFlowDataForPublicEndpoint(chatflow) return res.status(StatusCodes.OK).json(sanitized) ``` Ensure the sanitization function strips all `credential`, `password`, `apiKey`, and `secretKey` fields from `flowData`. --- ## References - `packages/server/src/controllers/chatflows/index.ts` lines 209-236 - `packages/server/src/utils/sanitizeFlowData.ts` lines 11-34 (exists only in unreleased HEAD) ## Credits - Shinobi Security - https://github.com/shinobisecurity

CVE-2026-41278 Affected Flowise Versions

1 component(s)
Fixed Versions:
3.1.0
Product / Package Ecosystem Affected Versions Fixed Version
flowise
npm
< 3.1.0
3.1.0

References

Frequently Asked Questions

What is CVE-2026-41278?
CVE-2026-41278 is a security vulnerability in Flowise involving Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Flowise versions are affected?
Affected versions include releases prior to 3.1.0 across affected packages: flowise.
What version fixes CVE-2026-41278?
Upgrading to 3.1.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is flowise affected?
Yes, flowise is affected in releases prior to 3.1.0. Upgrade your dependency to 3.1.0 or later.
What is the CVSS score of CVE-2026-41278?
CVE-2026-41278 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-41278?
CVE-2026-41278 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check npm dependencies for CVE-2026-41278?
Run the dependency tree command: 'npm ls flowise'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-w47f-j8rh-wx87",
  "modified" : "2026-04-24T21:00:58Z",
  "published" : "2026-04-17T21:34:30Z",
  "aliases" : [ "CVE-2026-41278" ],
  "summary" : "Flowise: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs",
  "details" : "### Summary\n\nThe `GET /api/v1/public-chatflows/:id` endpoint returns the full chatflow object **without sanitization** for public chatflows. Docker validation revealed this is worse than initially assessed: the `sanitizeFlowDataForPublicEndpoint` function does NOT exist in the released v3.0.13 Docker image. Both `public-chatflows` AND `public-chatbotConfig` return completely raw flowData including credential IDs, plaintext API keys, and password-type fields.\n\n### Root Cause\n\n```typescript\n// packages/server/src/controllers/chatflows/index.ts:218-220\nconst chatflow = await chatflowsService.getChatflowById(req.params.id)\nif (!chatflow) return res.status(StatusCodes.NOT_FOUND).json(...)\nif (chatflow.isPublic) return res.status(StatusCodes.OK).json(chatflow) // ← NO sanitization!\n```\n\n### Docker Validation (v3.0.13)\n\nCreated public chatflow with credential IDs and passwords in flowData:\n```json\n{\n  \"flowData\": \"{\\\"nodes\\\":[{\\\"data\\\":{\\\"credential\\\":\\\"e92a39bf-...\\\",\\\"inputs\\\":{\\\"password\\\":\\\"sk-supersecretkey123\\\",\\\"apiKey\\\":\\\"should-not-leak\\\"}}}]}\"\n}\n```\n\nThe `sanitizeFlowDataForPublicEndpoint` function only exists in unreleased HEAD, and even there, only `public-chatbotConfig` calls it — `public-chatflows` never does.\n\n### Impact\n\n- **Credential IDs** leaked — enables OAuth2 token theft chain (Finding 1)\n- **Plaintext API keys and passwords** leaked — direct third-party account compromise\n- **Node configurations** leaked — reveals internal architecture and endpoint URLs\n- Both `public-chatflows` and `public-chatbotConfig` are affected in the released version\n\n### Suggested Fix\n\nApply sanitization to both public endpoints:\n\n```typescript\nconst sanitized = sanitizeFlowDataForPublicEndpoint(chatflow)\nreturn res.status(StatusCodes.OK).json(sanitized)\n```\n\nEnsure the sanitization function strips all `credential`, `password`, `apiKey`, and `secretKey` fields from `flowData`.\n\n---\n\n## References\n\n- `packages/server/src/controllers/chatflows/index.ts` lines 209-236\n- `packages/server/src/utils/sanitizeFlowData.ts` lines 11-34 (exists only in unreleased HEAD)\n\n## Credits\n- Shinobi Security - https://github.com/shinobisecurity",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "flowise"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.1.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.0.13"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-w47f-j8rh-wx87"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-41278"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/FlowiseAI/Flowise"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-17T21:34:30Z",
    "nvd_published_at" : "2026-04-23T20:16:16Z"
  }
}