CVE-2026-56270: Flowise - Unauthenticated OAuth Secrets Disclosure via /api/v1/loginmethod Endpoint
Flowise before 3.1.0 (versions 3.0.13 and earlier) contains a missing authentication vulnerability in the /api/v1/loginmethod endpoint that allows unauthenticated users to retrieve an organization's complete SSO configuration, including OAuth client secrets in cleartext, by providing an organizationId parameter. Remote attackers can send a GET request to harvest sensitive API credentials for Google, Microsoft/Azure, GitHub, and Auth0 integrations. This affects FlowiseAI Cloud and self-hosted instances where the endpoint is exposed.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Flowiseto a version that resolves this vulnerability.Fixed in 3.1.0 - Compensating control
If the /api/v1/loginmethod endpoint is exposed to the internet, restrict network access to it (e.g., via firewall/ACL/WAF) so unauthenticated users cannot reach it.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-56270?
The severity of CVE-2026-56270 is high with a score of 7.5.
How do I fix CVE-2026-56270?
To fix CVE-2026-56270, upgrade to Flowise version 3.1.0 or later.
What vulnerability does CVE-2026-56270 describe?
CVE-2026-56270 describes a missing authentication vulnerability that allows unauthorized access to OAuth secrets via the /api/v1/loginmethod endpoint.
What information can be disclosed due to CVE-2026-56270?
CVE-2026-56270 can lead to the disclosure of an organization's complete SSO configuration, including OAuth client secrets in cleartext.
Who is affected by CVE-2026-56270?
CVE-2026-56270 affects users of Flowise versions 3.0.13 and earlier.