CVE-2026-69250
Received Received - Intake

OAuth2 Token Refresh SSRF in Flowise

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 OAuth2 token refresh endpoint POST /api/v1/oauth2-credential/refresh/:credentialId is unauthenticated by design and performs a server-side HTTP request to the credential-controlled accessTokenUrl without SSRF protections. Runtime validation confirmed that the endpoint was reachable without authentication, triggered outbound POST requests to an attacker-controlled server, reflected the full remote response body to the caller through tokenInfo, and sent client_id, client_secret, grant_type=refresh_token, and refresh_token in the request body. 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-69250
EUVD
EUVD-2026-52698

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
flowiseai flowise 3.1.3
flowise flowise 3.1.3

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an unauthenticated OAuth2 token refresh endpoint in Flowise versions before 3.1.3. The endpoint POST /api/v1/oauth2-credential/refresh/:credentialId allows attackers to trigger server-side HTTP requests to external URLs without proper protections. It exposes sensitive OAuth2 credentials like client_id, client_secret, and refresh_token during token refresh operations.

Detection Guidance

Check if your Flowise instance is running version 3.1.3 or later. Inspect network logs for unauthorized POST requests to /api/v1/oauth2-credential/refresh/:credentialId without authentication. Look for outbound HTTP requests to external servers from this endpoint.

Impact Analysis

An attacker could exploit this to exfiltrate OAuth2 credentials by sending them to a server they control. This could lead to unauthorized access to user accounts, data breaches, or further attacks using stolen credentials. The vulnerability enables non-blind SSRF, meaning the attacker can see the responses from their controlled server.

Compliance Impact

This vulnerability could lead to unauthorized data access or exfiltration, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. It risks non-compliance with confidentiality and integrity controls required by these regulations.

Mitigation Strategies

Upgrade Flowise to version 3.1.3 or later immediately. Review OAuth2 credential configurations to ensure accessTokenUrl points to trusted domains only. Monitor network traffic for suspicious outbound requests from the refresh endpoint.

Chat Assistant

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

EPSS Chart