CVE-2026-100609
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Summary
Flowise (npm packages flowise and flowise-components) through 3.1.4 looks up credentials by ID without filtering on the requesting user's workspace (findOneBy({ id: credentialId }) with no workspaceId condition) in several code paths: getAllOpenaiAssistants/getSingleOpenaiAssistant (GET /api/v1/openai-assistants and /api/v1/openai-assistants/:id), uploadFilesToAssistant (POST /api/v1/openai-assistants-file/upload/), deleteAssistant (DELETE /api/v1/assistants/:id, reachable by first importing a poisoned assistant row via POST /api/v1/export-import/import), and the shared helper used by getVoices (GET /api/v1/text-to-speech/voices). An authenticated user of one workspace can supply a credential UUID belonging to another workspace, causing the server to decrypt and use that workspace's OpenAI or ElevenLabs API key on the attacker's behalf. No patched version was available at the time of publication.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| FlowiseAI | Flowise | 0 <= 3.1.4 | affected |
| FlowiseAI | Flowise | 0 <= 3.1.4 | affected |
Weaknesses
- CWE-639: Authorization Bypass Through User-Controlled Key
References
- https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-27w2-26m5-x82c
- https://www.vulncheck.com/advisories/flowise-through-3.1.4-insecure-direct-object-reference-via-credential
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.