Is CVE-2026-100609 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-100609 being exploited in the wild.

How severe is CVE-2026-100609?

Medium severity, with a CVSS score of 6.8, published 26 September 2026.

Which products and versions are affected?

FlowiseAI Flowise through 3.1.4; FlowiseAI Flowise-Components through 3.1.4.

Is there a fix for CVE-2026-100609?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-100609 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-100609?

Check whether you run FlowiseAI Flowise or FlowiseAI Flowise-Components at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-100609: Flowise credential lookup authorization bypass

CVE-2026-100609 · Severity: medium · CVSS 6.8 · Published 2026-09-26

Flowise, an open-source AI workflow platform that manages API credentials for third-party services like OpenAI and ElevenLabs, fails to validate that users can only access credentials within their own workspace. An attacker with any account can submit another user's credential UUID and trick Flowise into decrypting and using that credential to make API calls, potentially gaining unauthorized access to expensive third-party APIs or hijacking AI workflows.

Technologies: FlowiseAI Flowise, FlowiseAI Flowise-Components. Vendors: FlowiseAI.

Quick answers

Is CVE-2026-100609 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-100609 being exploited in the wild.
How severe is CVE-2026-100609?: Medium severity, with a CVSS score of 6.8, published 26 September 2026.
Which products and versions are affected?: FlowiseAI Flowise through 3.1.4; FlowiseAI Flowise-Components through 3.1.4.
Is there a fix for CVE-2026-100609?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-100609 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-100609?: Check whether you run FlowiseAI Flowise or FlowiseAI Flowise-Components at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an insecure direct object reference (IDOR) affecting credential lookup across four API endpoints: getAllOpenaiAssistants, uploadFilesToAssistant, deleteAssistant, and getVoices. Each endpoint uses findOneBy({ id: credentialId }) without filtering by workspaceId, allowing any authenticated user to supply a foreign credential UUID and trigger decryption and use of that workspace's API key. The attack requires authentication and knowledge of a valid credential UUID from another workspace; exploitation is verified through error differential analysis showing successful credential use.

Affected products

FlowiseAI flowise through 3.1.4
FlowiseAI flowise-components through 3.1.4

Timeline

2026-09-26: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.