CVE-2026-70636

Received Received - Intake

Authentication Bypass in Flowise AI Platform

Publication date: 2026-08-06

Last updated on: 2026-08-06

Assigner: VulnCheck

Description

Flowise through 3.1.4 contains an authentication bypass vulnerability that allows unauthenticated attackers to access the OAuth2 credential refresh endpoint by exploiting prefix-based whitelist matching in the authentication middleware defined in packages/server/src/utils/constants.ts. Attackers can send a POST request to the oauth2-credential refresh route with a trailing credential identifier to bypass all authentication and authorization checks, triggering unauthorized OAuth token rotation against credentials belonging to any workspace and potentially disrupting dependent OAuth integrations. This is a bypass of CVE-2026-41273.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-06

Last Modified

2026-08-06

Generated

2026-08-07

AI Q&A

2026-08-07

EPSS Evaluated

N/A

NVD

CVE-2026-70636

Affected Vendors & Products

Vendor	Product	Version / Range
flowise	flowise	3.1.4

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-862	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

Executive Summary

This vulnerability is an authentication bypass in Flowise versions up to 3.1.4. It allows unauthenticated attackers to access the OAuth2 credential refresh endpoint by exploiting a flaw in the authentication middleware. Attackers can send a POST request with a trailing credential identifier to bypass authentication checks and trigger unauthorized OAuth token rotation for any workspace's credentials.

Detection Guidance

Check Flowise logs for unusual POST requests to the oauth2-credential/refresh endpoint with trailing credential identifiers. Monitor for unauthorized OAuth token rotations or disruptions in dependent integrations.

Impact Analysis

This vulnerability allows attackers to disrupt OAuth integrations by forcing unauthorized token rotations. This could lead to service disruptions, loss of access to third-party services, and potential data exposure if OAuth tokens are compromised. Systems relying on Flowise for authentication may be affected.

Compliance Impact

This vulnerability could impact compliance by enabling unauthorized access to OAuth tokens, potentially leading to data breaches. GDPR requires protecting personal data, and HIPAA requires safeguarding health information. A breach could result in non-compliance, legal penalties, and reputational damage.

Mitigation Strategies

Upgrade Flowise to a version beyond 3.1.4 that patches this vulnerability. If immediate upgrade is not possible, restrict access to the oauth2-credential/refresh endpoint via network controls or disable OAuth integrations temporarily.

Hi! I’m here to help you understand CVE-2026-70636. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70