CVE-2026-70474
Received Received - Intake

OAuth2 Credential Manipulation in Flowise

Publication date: 2026-08-04

Last updated on: 2026-08-04

Assigner: GitHub, Inc.

Description
Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to 3.1.3, Flowise has three OAuth2 credential endpoints that look up credentials by id alone with no workspaceId filter. The authorize, callback, and refresh handlers query the Credential table by id only; callback and refresh are whitelisted from authentication. This allows any authenticated user to initiate OAuth2 flows against credentials belonging to other workspaces, allows an unauthenticated attacker to forge OAuth2 callbacks to overwrite tokens in any credential, and allows an unauthenticated attacker to refresh tokens for any credential. The affected routes include /api/v1/oauth2-credential/authorize/<VICTIM_CREDENTIAL_UUID>, /api/v1/oauth2-credential/callback?code=ATTACKER_AUTH_CODE&state=<VICTIM_CREDENTIAL_UUID>, and /api/v1/oauth2-credential/refresh/<VICTIM_CREDENTIAL_UUID>. This issue is fixed in version 3.1.3.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-04
Last Modified
2026-08-04
Generated
2026-08-04
AI Q&A
2026-08-04
EPSS Evaluated
N/A
NVD
CVE-2026-70474
EUVD
EUVD-2026-52855

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
flowise flowise 3.1.3
flowiseai flowise to 3.1.3 (exc)
flowiseai flowise 3.1.3

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Flowise, an AI application builder, in versions 3.1.2 and earlier. It involves three OAuth2 credential endpoints that do not enforce workspace isolation. These endpoints query credentials by ID alone without checking workspace ownership. The callback and refresh endpoints are also whitelisted from authentication, allowing unauthenticated access. Attackers can exploit this to access credentials across workspaces, forge callbacks to overwrite tokens, or refresh tokens without authentication.

Detection Guidance

Check Flowise logs for suspicious OAuth2 callback or refresh requests targeting credentials not in the current workspace. Monitor network traffic for unauthorized access to /api/v1/oauth2-credential/authorize/<VICTIM_CREDENTIAL_UUID>, /api/v1/oauth2-credential/callback, or /api/v1/oauth2-credential/refresh/<VICTIM_CREDENTIAL_UUID> endpoints.

Impact Analysis

If you use Flowise versions 3.1.2 or earlier, attackers could steal OAuth2 tokens for external services like Microsoft 365 or Google Workspace. They can access credentials across workspaces, overwrite tokens, or refresh tokens without authentication. This could lead to unauthorized access to your external services and data.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating compliance requirements under GDPR and HIPAA. GDPR requires protecting personal data, while HIPAA mandates safeguarding protected health information. Unauthorized token access may result in data breaches, leading to legal penalties and reputational damage.

Mitigation Strategies

Upgrade Flowise to version 3.1.3 or later. Ensure all OAuth2 credential endpoints enforce workspaceId filtering. Remove callback and refresh endpoints from authentication whitelists. Implement signed state tokens for callbacks and prevent direct access token exposure in responses.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-70474. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart