CVE-2026-70474 FlowiseAI CVE debrief

Who should care

Flowise users and administrators should be aware of this vulnerability and take steps to patch or mitigate it. Affected operator, platform, vulnerability-management, and security-team impact should be considered when evaluating this vulnerability. Users should prioritize patching to prevent potential credential compromise and review compensating controls for exposed systems while remediation is scheduled and verified. Monitoring, detection, and logs for exposed assets that need extra review should also be checked. Exceptions, retest remediated assets, and close the item only after evidence is documented are also important steps to take. Asset inventory and source tracking can help with this process. Rollback/change windows may be necessary for some environments. Vendor patch guidance should be reviewed and followed. Exposure review and compensating controls can help mitigate the vulnerability until patching can occur. Compensating controls, such as restricting access to OAuth2 credential endpoints and monitoring for suspicious OAuth2 flow activity, can help reduce the risk of this vulnerability. Additionally, reviewing and restricting access to OAuth2 credential endpoints can help prevent exploitation. Tracking exceptions, retesting remediated assets, and closing the item only after evidence is documented are also crucial steps to take. Compensating controls, such as implementing additional security measures, can help mitigate the vulnerability. Monitoring and detection can help identify potential exploitation. Asset inventory and source tracking can help with this process. Rollback/change windows may be necessary for some environments. Vendor patch guidance should be reviewed and followed. Exposure review and compensating controls can help mitigate the vulnerability until patching can occur. Compensating controls, such as restricting access to OAuth2 credential endpoints and monitoring for suspicious OAuth2 flow activity, can help reduce the risk of this vulnerability. Additionally, reviewing and restricting access to OAuth2 credential endpoints can help prevent exploitation. Tracking exceptions, retesting remediated assets, and closing the item only after证据 is

Technical summary

Flowise has three OAuth2 credential endpoints that look up credentials by id alone with no workspaceId filter. This allows any authenticated user to initiate OAuth2 flows against credentials belonging to other workspaces, allows an unauthenticated attacker to forge OAuth2 callbacks to overwrite tokens in any credential, and allows an unauthenticated attacker to refresh tokens for any credential. The affected routes include /api/v1/oauth2-credential/authorize/<VICTIM_CREDENTIAL_UUID>, /api/v1/oauth2-credential/callback?code=ATTACKER_AUTH_CODE&state=<VICTIM_CREDENTIAL_UUID>, and /api/v1/oauth2-credential/refresh/<VICTIM_CREDENTIAL_UUID>.

Defensive priority

Flowise users should prioritize patching to prevent potential credential compromise.

Recommended defensive actions

• Patch Flowise to version 3.1.3 or later
• Review and restrict access to OAuth2 credential endpoints
• Monitor for suspicious OAuth2 flow activity
• Implement additional security measures
• Review vendor patch guidance
• Conduct exposure review
• Track exceptions and retest remediated assets

Evidence notes

The CVE description indicates that Flowise has three OAuth2 credential endpoints that look up credentials by id alone with no workspaceId filter, allowing any authenticated user to initiate OAuth2 flows against credentials belonging to other workspaces, and allowing an unauthenticated attacker to forge OAuth2 callbacks to overwrite tokens in any credential and refresh tokens for any credential.

Official resources