CVE-2026-70636: CWE-862 Missing Authorization in FlowiseAI Flowise
Flowise versions up to 3.1.4 contain an authentication bypass vulnerability that allows unauthenticated attackers to access the OAuth2 credential refresh endpoint. This occurs due to prefix-based whitelist matching in the authentication middleware, enabling attackers to bypass authentication and authorization checks. Exploitation can lead to unauthorized OAuth token rotation for any workspace's credentials, potentially disrupting OAuth integrations. This vulnerability is a bypass of a previously identified issue (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 send a specially crafted POST request to the oauth2-credential refresh route with a trailing credential identifier, bypassing all authentication and authorization checks. This allows unauthorized rotation of OAuth tokens for credentials belonging to any workspace, which may disrupt dependent OAuth integrations. This vulnerability is a bypass of CVE-2026-41273.
Potential Impact
Unauthenticated attackers can bypass authentication and authorization controls to trigger OAuth token rotation for any workspace's credentials. This can disrupt OAuth integrations that rely on these credentials, potentially causing denial of service or unauthorized access to integrated services. The vulnerability has a high severity with a CVSS 4.0 score of 8.7, indicating it is exploitable remotely without privileges or user interaction.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the OAuth2 credential refresh endpoint and monitor for unusual POST requests targeting this route. Avoid exposing the service to untrusted networks and consider implementing additional access controls or network-level restrictions to mitigate exploitation risk.
CVE-2026-70636: CWE-862 Missing Authorization in FlowiseAI Flowise
Description
Flowise versions up to 3.1.4 contain an authentication bypass vulnerability that allows unauthenticated attackers to access the OAuth2 credential refresh endpoint. This occurs due to prefix-based whitelist matching in the authentication middleware, enabling attackers to bypass authentication and authorization checks. Exploitation can lead to unauthorized OAuth token rotation for any workspace's credentials, potentially disrupting OAuth integrations. This vulnerability is a bypass of a previously identified issue (CVE-2026-41273).
CVSS v4.0
Score 8.7high
Affected software
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 send a specially crafted POST request to the oauth2-credential refresh route with a trailing credential identifier, bypassing all authentication and authorization checks. This allows unauthorized rotation of OAuth tokens for credentials belonging to any workspace, which may disrupt dependent OAuth integrations. This vulnerability is a bypass of CVE-2026-41273.
Potential Impact
Unauthenticated attackers can bypass authentication and authorization controls to trigger OAuth token rotation for any workspace's credentials. This can disrupt OAuth integrations that rely on these credentials, potentially causing denial of service or unauthorized access to integrated services. The vulnerability has a high severity with a CVSS 4.0 score of 8.7, indicating it is exploitable remotely without privileges or user interaction.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to the OAuth2 credential refresh endpoint and monitor for unusual POST requests targeting this route. Avoid exposing the service to untrusted networks and consider implementing additional access controls or network-level restrictions to mitigate exploitation risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-04T20:17:18.298Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a75070dbf8831d5395f5c6d
Added to database: 08/06/2026, 22:13:33 UTC
Last enriched: 08/06/2026, 22:41:06 UTC
Last updated: 08/07/2026, 03:54:59 UTC
Views: 6
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.