Flowise
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.1.0
Fixed in 3.1.0
Mitigation
Upgrade Flowise to 3.1.0 or later.
References
- Vendor advisory github.com/FlowiseAI/Flowise/security/advisori…
Timeline
Days relative to CVE publicationFirst public PoC 56 days after publication; not in CISA KEV. First PoC: nuclei template: Flowise <= 3.0.13 - Unauthenticated OAuth Configuration Disclosure (nuclei template, 19 Aug 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: Flowise <= 3.0.13 - Unauthenticated OAuth Configuration Disclosure | 19 Aug 2026 | 14 Nov 2026 |