{"id":"GHSA-4jpm-cgx2-8h37","summary":"Flowise: Sensitive Data Leak in public-chatbotConfig ","details":"### Summary\n\n`/api/v1/public-chatbotConfig/:id `ep exposes sensitive data including API keys, HTTP authorization headers and internal configuration without any authentication. An attacker with knowledge just of a chatflow UUID can retrieve credentials stored in password type fields and HTTP headers, leading to credential theft and more.\n\n### Details\n\nKnowledge of chatflow UUID can be obtained from embedded chat widgets, referrer headers or logs and it's the only prerequest. \n\n`getSinglePublicChatbotConfig` function in `packages/server/src/services/chatflows/index.ts` returns the full **flowData** object without authorization check or data sanitization.\n\nThere is a comment as **\"Safe as public endpoint as chatbotConfig doesn't contain sensitive credential\"** but **flowData** does contain sensitive data such as:\n\n`type: 'password'` fields are stored in plaintext (unstructuredAPIKey in S3File node).\nHTTP Authorization headers in POST / GET Requests nodes.\nInternal API endpoints and webhook URLs.\n\n### PoC\n\n- Add an S3 File node, set \"File Processing Method\" to \"Unstructured\".\n- Enter an API key in \"Unstructured API KEY\" field or add a Requests Post node with Authorization header.\n- Save the chatflow.\n\n`curl -s \"https://localhost/api/v1/public-chatbotConfig/{CHATFLOW_UUID}\"`\n\nResponse:\n\n```\n{\n  \"flowData\": \"{...\\\"unstructuredAPIKey\\\":\\\"victim_key\\\"...\\\"requestsPostHeaders\\\":\\\"Bearer victim_token\\\"...}\"\n}\n```\n\n### Impact\n\nImpacts all Flowise Cloud users with chatflows containing password type fields or any HTTP headers. And self hosted Flowise instances exposed to the internet.","aliases":["CVE-2026-41266"],"modified":"2026-05-05T16:11:51.492559Z","published":"2026-04-16T21:44:49Z","database_specific":{"severity":"HIGH","github_reviewed":true,"github_reviewed_at":"2026-04-16T21:44:49Z","nvd_published_at":"2026-04-23T20:16:15Z","cwe_ids":["CWE-200","CWE-522","CWE-862"]},"references":[{"type":"WEB","url":"https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-4jpm-cgx2-8h37"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-41266"},{"type":"PACKAGE","url":"https://github.com/FlowiseAI/Flowise"}],"affected":[{"package":{"name":"flowise","ecosystem":"npm","purl":"pkg:npm/flowise"},"ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.1.0"}]}],"database_specific":{"last_known_affected_version_range":"\u003c= 3.0.13","source":"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/04/GHSA-4jpm-cgx2-8h37/GHSA-4jpm-cgx2-8h37.json"}}],"schema_version":"1.9.0","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:N/VI:N/VA:N/SC:H/SI:N/SA:N"}]}