Is CVE-2026-100606 exploited in the wild?

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

How severe is CVE-2026-100606?

High severity, with a CVSS score of 7.7, published 26 September 2026.

Which products and versions are affected?

FlowiseAI Flowise through 3.1.4.

Is there a fix for CVE-2026-100606?

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-100606 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-100606?

Check whether you run FlowiseAI Flowise 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-100606: Flowise authentication bypass in SSO login path

CVE-2026-100606 · Severity: high · CVSS 7.7 · Published 2026-09-26

Flowise is an enterprise AI workflow automation platform that uses single sign-on (SSO) for user authentication in platform mode. An attacker who can authenticate at any configured SSO provider using a pending invitee's email address can take over an open invitation and gain full access to the invited user's account and organization membership, without needing the invitation token that was emailed to the victim. This makes every pending invitation a potential foothold into enterprise deployments.

Technologies: FlowiseAI Flowise. Vendors: FlowiseAI.

Quick answers

Is CVE-2026-100606 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-100606 being exploited in the wild.
How severe is CVE-2026-100606?: High severity, with a CVSS score of 7.7, published 26 September 2026.
Which products and versions are affected?: FlowiseAI Flowise through 3.1.4.
Is there a fix for CVE-2026-100606?: 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-100606 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-100606?: Check whether you run FlowiseAI Flowise 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 exists in the SSO verifyAndLogin function (SSOBase.ts:80-94) which passes the server-stored invitation tempToken to the register handler instead of requiring a caller-supplied token. The register validation chain then validates against the database-stored token that was just copied from the user record, rather than an external proof of email ownership, allowing trivial bypass. An attacker needs only an email match at any configured SSO provider; the attack succeeds during the 24-hour invitation window and requires no user interaction beyond SSO authentication.

Affected products

FlowiseAI Flowise through 3.1.4

Timeline

2026-09-26: disclosed
2026-09-10: advisory: GitHub Security Advisory GHSA-vf3j-89vf-r697 published

References

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