CVE-2026-100607: Improper Authentication in FlowiseAI Flowise
Flowise through 3.1.4 resolves SSO and local-password users solely by email without storing provider or subject identifier bindings, allowing attackers to authenticate as any existing user by claiming their email at any configured SSO provider. Attackers can gain complete account access including chatflows, credentials, and API keys by authenticating through a different SSO provider or local password than the victim's original registration method.
AI Analysis
Technical Summary
FlowiseAI Flowise through version 3.1.4 has an authentication design flaw where user identity is resolved only by email address, ignoring the SSO provider or subject identifier bindings. This allows an attacker to impersonate any existing user by authenticating through a different SSO provider or local password than the victim's original registration method. As a result, attackers can gain complete access to the victim's account and sensitive data such as chatflows, credentials, and API keys. The vulnerability has a CVSS 4.0 score of 9.2, indicating critical severity.
Potential Impact
An attacker can fully compromise any user account by exploiting this vulnerability, gaining unauthorized access to sensitive application data and credentials. This can lead to data theft, unauthorized actions, and potential further compromise of integrated systems through exposed API keys.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to trusted users and monitor for suspicious authentication attempts. Avoid using multiple SSO providers with the same email addresses if possible.
CVE-2026-100607: Improper Authentication in FlowiseAI Flowise
Description
Flowise through 3.1.4 resolves SSO and local-password users solely by email without storing provider or subject identifier bindings, allowing attackers to authenticate as any existing user by claiming their email at any configured SSO provider. Attackers can gain complete account access including chatflows, credentials, and API keys by authenticating through a different SSO provider or local password than the victim's original registration method.
CVSS v4.0
Score 9.2critical
Affected software
FlowiseAI
Flowise
pkg:github/flowiseai/FlowiseRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
FlowiseAI Flowise through version 3.1.4 has an authentication design flaw where user identity is resolved only by email address, ignoring the SSO provider or subject identifier bindings. This allows an attacker to impersonate any existing user by authenticating through a different SSO provider or local password than the victim's original registration method. As a result, attackers can gain complete access to the victim's account and sensitive data such as chatflows, credentials, and API keys. The vulnerability has a CVSS 4.0 score of 9.2, indicating critical severity.
Potential Impact
An attacker can fully compromise any user account by exploiting this vulnerability, gaining unauthorized access to sensitive application data and credentials. This can lead to data theft, unauthorized actions, and potential further compromise of integrated systems through exposed API keys.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to trusted users and monitor for suspicious authentication attempts. Avoid using multiple SSO providers with the same email addresses if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-26T02:30:34.352Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab7c99ff7a7c5410652fca3
Added to database: 09/26/2026, 13:33:19 UTC
Last enriched: 09/26/2026, 14:19:21 UTC
Last updated: 09/27/2026, 02:20:04 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.