CVE-2026-70636: Missing Authorization in FlowiseAI Flowise
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.
AI Analysis
Technical Summary
CVE-2026-70636 is an authentication bypass vulnerability in Flowise through version 3.1.4. The flaw arises from prefix-based whitelist matching in the authentication middleware located in packages/server/src/utils/constants.ts. Attackers can exploit this by sending a POST request to the oauth2-credential refresh route with a trailing credential identifier, bypassing all authentication and authorization checks. This triggers unauthorized OAuth token rotation for credentials belonging to any workspace, which may disrupt dependent OAuth integrations. This vulnerability is a bypass of CVE-2026-41273 and has a CVSS 4.0 base score of 8.7, indicating high severity.
Potential Impact
Unauthenticated attackers can bypass authentication and authorization to rotate OAuth tokens for any workspace's credentials. This unauthorized token rotation can disrupt OAuth integrations that depend on these credentials, potentially causing service interruptions or unauthorized access through compromised tokens.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch is currently documented. Until a patch is available, restrict access to the OAuth2 credential refresh endpoint and monitor for suspicious POST requests targeting this route. Follow vendor updates closely for any forthcoming official fixes.
CVE-2026-70636: Missing Authorization in FlowiseAI Flowise
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 v4.0
Score 8.7high
Affected software
FlowiseAI
Flowise
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-70636 is an authentication bypass vulnerability in Flowise through version 3.1.4. The flaw arises from prefix-based whitelist matching in the authentication middleware located in packages/server/src/utils/constants.ts. Attackers can exploit this by sending a POST request to the oauth2-credential refresh route with a trailing credential identifier, bypassing all authentication and authorization checks. This triggers unauthorized OAuth token rotation for credentials belonging to any workspace, which may disrupt dependent OAuth integrations. This vulnerability is a bypass of CVE-2026-41273 and has a CVSS 4.0 base score of 8.7, indicating high severity.
Potential Impact
Unauthenticated attackers can bypass authentication and authorization to rotate OAuth tokens for any workspace's credentials. This unauthorized token rotation can disrupt OAuth integrations that depend on these credentials, potentially causing service interruptions or unauthorized access through compromised tokens.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch is currently documented. Until a patch is available, restrict access to the OAuth2 credential refresh endpoint and monitor for suspicious POST requests targeting this route. Follow vendor updates closely for any forthcoming official fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-04T20:17:18.298Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a75070dbf8831d5395f5c6d
Added to database: 08/06/2026, 22:13:33 UTC
Last enriched: 08/14/2026, 15:51:53 UTC
Last updated: 09/21/2026, 22:01:37 UTC
Views: 41
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.