CriticalVulnerability
GHSA-qgvm-j2hm-6m38: Flowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected service
- Identifiers
- CVE-2026-70478GHSA-qgvm-j2hm-6m38
- Published
- Record updated
- Affected
- flowise <= 3.1.2
- Fixed in
- 3.1.3
- released June 25, 2026, 40 days before disclosure
- Known exploitation
- Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
- EPSS
- 0.6%
Summary
Flowise's OAuth2 token refresh endpoint, POST /api/v1/oauth2-credential/refresh/:credentialId, is listed in WHITELIST_URLS and so requires no authentication. It decrypts the stored credential, sends a refresh request to the configured OAuth provider, and returns the new access_token in the response body. An attacker who obtains a credential ID can use this to steal access tokens for the victim's connected services, such as Google or Microsoft accounts.
Mitigation
Suggested fix: remove the refresh endpoint from WHITELIST_URLS in constants.ts and add an authentication check in the route handler.
Affected packages in the Exposure Registry
Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.
- flowisenpmLLM dependency since 2024-03-12
Related items
- MediumCVE-2026-121936: easyVoice server-side request forgery through openaiBaseUrl in /api/v1/ttsSimilar attack · NVD/CVE Database
- MediumCVE-2026-118628: MLflow get-artifacts server-side request forgery information disclosureSimilar attack · NVD/CVE Database
- HighCVE-2026-118625: MLflow Tracking Server privilege escalation via get_endpointsSimilar attack · NVD/CVE Database
- InfoWhen trust becomes the payload: Inside the threats, etc quarterly reportSimilar attack · Elastic Security Labs
- MediumCritical Langflow flaws enable authentication bypass and RCESimilar attack · CSO Online