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.
CVE-2026-56270
This medium-severity CVE scores 5.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 5.3(low)
- EPSS
- 30.4%
- KEV
- Not listed
Published
April 16, 2026
Last Modified
June 26, 2026
Advisory Details (2)
Auto-updated Jun 25, 2026Unauthenticated Information Disclosure of OAuth Secrets (Cleartext) via GET Request · Advisory · FlowiseAI/Flowise · GitHub
https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-6pcv-j4jx-m4vxFlowise - Unauthenticated OAuth Secrets Disclosure via /api/v1/loginmethod Endpoint | Advisories | VulnCheck
https://www.vulncheck.com/advisories/flowise-unauthenticated-oauth-secrets-disclosure-via-api-v1-loginmethod-endpointVendor Advisories for CVE-2026-56270(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 28× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 04:08 UTCOSV refresh
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
Show 3 moreShow fewer
- 2026-06-25 15:47 UTCNVD updateCVSS v3 → 7.5 · CVSS v4 → 8.7 · severity → HIGH
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-24 14:03 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-56270?
When was CVE-2026-56270 disclosed?
Is CVE-2026-56270 actively exploited?
What is the CVSS score of CVE-2026-56270?
How do I remediate CVE-2026-56270?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-56270
Is Your Infrastructure Affected by CVE-2026-56270?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.