CVE-2026-70636

Flowise 3.1.4 Authentication Bypass via OAuth2 Credential Refresh Endpoint

Published Aug 6, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Flowise version 3.1.4 implements an authentication middleware that checks user permissions by comparing request URLs against a prefix‑based whitelist. A flaw in this matching allows any caller to append a credential identifier to the oauth2-credential refresh route and bypass both authentication and authorization checks. As a result, an unauthenticated attacker can trigger an OAuth token rotation for any workspace credential, potentially causing disruption to integrated services that rely on those tokens.

Affected Systems

The vulnerability is present in all FlowiseAI Flowise deployments running version 3.1.4 or earlier. No specific environment or operating system is required; the flaw exists in the application code itself.

Risk and Exploitability

The vulnerability has a CVSS base score of 8.7, indicating high severity. EPSS is not available and the entry is not listed in CISA KEV, suggesting limited public exploitation data. Attackers can exploit the flaw by sending a POST request directly to the /oauth2-credential/refresh endpoint with an appended credential identifier, which can be performed from any network that can reach the Flowise instance. Bypassing authentication also removes authorization checks, so the attacker can target any workspace credential. The attack vector is inferred to be both local and remote, depending on network exposure of the Flowise service.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a custom patch that corrects the authentication middleware to enforce strict prefix matching, rejecting any appended credential identifiers.
  • Disable or protect the /oauth2-credential/refresh endpoint by adding explicit access controls or removing the route from public APIs if not required.
  • Restrict access to the endpoint via network isolation, such as a firewall or reverse proxy, allowing only trusted hosts.

Generated by OpenCVE AI on August 7, 2026 at 00:56 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Flowiseai
Flowiseai flowise
Vendors & Products Flowiseai
Flowiseai flowise
Type Values Removed Values Added
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.
Title Flowise 3.1.4 Authentication Bypass via OAuth2 Credential Refresh Endpoint
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 14, 2026, 4:51 PM
Reserved
Aug 4, 2026, 8:17 PM
Status
Analyzed
Published
Aug 6, 2026, 10:18 PM
Modified
Oct 24, 2026, 3:10 PM