{"id":"CVE-2026-41278","aliases":["EUVD-2026-25297","GHSA-w47f-j8rh-wx87"],"status":"published","title":"Flowise: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs","description":"Flowise is a drag \u0026 drop user interface to build a customized large language model flow. Prior to 3.1.0, 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. This vulnerability is fixed in 3.1.0.","severity":{"version":"4.0","score":8.7,"vector":"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","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00421,"percentile":0.36718,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-200"],"published":"2026-04-17T21:34:30Z","modified":"2026-10-28T02:30:52Z","fixes":[{"ecosystem":"npm","package":"flowise","fixed_in":["3.1.0"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"flowise","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"3.0.13"},{"fixed":"3.1.0"}]}]},{"source":"osv","ecosystem":"npm","package":"flowise","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.1.0"}]}]}],"products":[{"vendor":"flowiseai","product":"flowise"}],"references":[{"url":"https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-w47f-j8rh-wx87","tags":["x_refsource_CONFIRM","Exploit","Vendor Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-41278","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-w47f-j8rh-wx87"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/41xxx/CVE-2026-41278.json","tags":["advisory"]},{"url":"https://github.com/FlowiseAI/Flowise","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-41278","title":"Flowise: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs","description":"Flowise is a drag \u0026 drop user interface to build a customized large language model flow. Prior to 3.1.0, 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. This vulnerability is fixed in 3.1.0.","status":"published","published":"2026-04-23T19:52:20.973Z","modified":"2026-04-24T13:39:52.9Z","cvss":[{"version":"4.0","score":8.7,"vector":"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","level":"high","assessor":"cna"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T13:40:57.334596Z"}],"euvd":[{"id":"EUVD-2026-25297","description":"Flowise is a drag \u0026 drop user interface to build a customized large language model flow. Prior to 3.1.0, 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. This vulnerability is fixed in 3.1.0.","status":"published","published":"2026-04-23T19:52:20Z","modified":"2026-04-24T13:39:52Z","cvss":[{"version":"4.0","score":8.7,"vector":"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","level":"high"}],"updated_at":"2026-11-02T19:24:18.636842Z"}],"ghsa":[{"id":"GHSA-w47f-j8rh-wx87","title":"Flowise: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs","description":"### 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","status":"published","published":"2026-04-17T21:34:30Z","modified":"2026-04-24T21:00:59Z","cvss":[{"version":"4.0","score":8.7,"vector":"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","level":"high"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T14:39:57.650091Z"}],"nvd":[{"id":"CVE-2026-41278","description":"Flowise is a drag \u0026 drop user interface to build a customized large language model flow. Prior to 3.1.0, 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. This vulnerability is fixed in 3.1.0.","status":"published","published":"2026-04-23T20:16:16.55Z","modified":"2026-10-26T21:10:00.17Z","cvss":[{"version":"4.0","score":8.7,"vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high","assessor":"primary"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T14:12:15.867234Z"}],"osv":[{"id":"CVE-2026-41278","title":"Flowise: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs","description":"Flowise is a drag \u0026 drop user interface to build a customized large language model flow. Prior to 3.1.0, 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. This vulnerability is fixed in 3.1.0.","status":"published","published":"2026-04-23T19:52:20.973Z","modified":"2026-10-28T02:30:52.915404673Z","cvss":[{"version":"4.0","score":8.7,"vector":"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","level":"high"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T15:45:03.764807Z"},{"id":"GHSA-w47f-j8rh-wx87","title":"Flowise: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs","description":"### 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","status":"published","published":"2026-04-17T21:34:30Z","modified":"2026-05-05T16:26:27.717521Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"},{"version":"4.0","score":8.7,"vector":"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","level":"high"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T15:46:58.04805Z"}]}}
