CVE-2026-100609: Flowise through 3.1.4 Insecure Direct Object Reference via Credential

Published Sep 26, 2026
·
Updated

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

2 affected components
npm/flowise<=3.1.4
npm/flowise-components<=3.1.4

Event History

Sep 26, 2026
CVE Published
via MITRE·01:22 PM
Data Sourced
via MITRE·01:22 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is realistically exposed?

Deployments with multiple workspaces are exposed when credentials belonging to one workspace can be referenced by an authenticated user in another workspace. The affected packages are flowise and flowise-components through 3.1.4.

2

What does an attacker need to exploit this?

The attacker needs an authenticated account in a workspace and a credential UUID belonging to a different workspace. They can then provide that UUID to an affected API path, causing the server to decrypt and use the other workspace's OpenAI or ElevenLabs key.

3

Which API paths should be prioritized for review or restriction?

The identified paths are GET /api/v1/openai-assistants, GET /api/v1/openai-assistants/:id, POST /api/v1/openai-assistants-file/upload/, DELETE /api/v1/assistants/:id after importing a poisoned assistant row through POST /api/v1/export-import/import, and GET /api/v1/text-to-speech/voices.

4

Is a patched release available?

No patched version was available at the time of publication.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203