CVE-2026-70478
Received Received - Intake

Authentication Bypass in Flowise via Unprotected OAuth Refresh Endpoint

Publication date: 2026-08-04

Last updated on: 2026-08-04

Assigner: GitHub, Inc.

Description
Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.3, the POST /api/v1/oauth2-credential/refresh/:credentialId endpoint is included in WHITELIST_URLS and requires no authentication. The endpoint decrypts the stored credential, sends a refresh request to the configured OAuth provider with the client secret and refresh token, and returns the refreshed access_token in the response body. An attacker with a credential ID can use the token to access the victim's connected service and can also exhaust refresh-token quota. This issue is fixed in 3.1.3.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-04
Last Modified
2026-08-04
Generated
2026-08-05
AI Q&A
2026-08-04
EPSS Evaluated
N/A
NVD
CVE-2026-70478
EUVD
EUVD-2026-52912

Affected Vendors & Products

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

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Flowise allows unauthenticated access to an OAuth2 token refresh endpoint. The endpoint at POST /api/v1/oauth2-credential/refresh/:credentialId is whitelisted, meaning it requires no authentication. An attacker can exploit this by using a credential ID to call the endpoint, which decrypts stored credentials, sends a refresh request to the OAuth provider, and returns the new access token in the response. This token can then be used to access the victim's connected services.

Detection Guidance

Check if the endpoint POST /api/v1/oauth2-credential/refresh/:credentialId is accessible without authentication. Use tools like curl to test unauthenticated access: curl -X POST http://<target>/api/v1/oauth2-credential/refresh/123. If the endpoint responds with a token, it is vulnerable.

Impact Analysis

An attacker could gain full access to your third-party accounts linked through Flowise, such as Google, Microsoft, or GitHub. They could also exhaust refresh token quotas, leading to denial-of-service conditions for your connected services.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's security requirements. It may result in data breaches, unauthorized data processing, and non-compliance with regulatory obligations.

Mitigation Strategies

Upgrade Flowise to version 3.1.3 or later to remove the unauthenticated endpoint from the whitelist. If upgrading is not immediately possible, restrict access to the endpoint by adding authentication requirements or removing it from the whitelist.

Chat Assistant

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

EPSS Chart