CVE-2026-70474 FlowiseAI CVE debrief

Who should care

Defenders responsible for Flowise deployments should assess exposure and prioritize upgrading to version 3.1.3 or later. Restricting access to OAuth2 credential endpoints and monitoring for suspicious activity are also recommended.

Why it matters

CVE-2026-70474 allows unauthorized access and token manipulation in Flowise OAuth2 credential endpoints. Defenders should prioritize verifying and upgrading to Flowise version 3.1.3 or later, and restrict access to OAuth2 credential endpoints. Evidence is based on official CVE and NVD records, and vendor advisories.

• An unauthenticated attacker can forge OAuth2 callbacks to overwrite tokens in any credential
• An unauthenticated attacker can refresh tokens for any credential
• Any authenticated user can initiate OAuth2 flows against credentials belonging to other workspaces

Technical summary

Flowise has three OAuth2 credential endpoints that look up credentials by id alone with no workspaceId filter. The authorize, callback, and refresh handlers query the Credential table by id only; callback and refresh are whitelisted from authentication. 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.

Defensive priority

Defenders should prioritize verifying and upgrading to Flowise version 3.1.3 or later, and restrict access to OAuth2 credential endpoints.

Recommended defensive actions

• Verify and upgrade to Flowise version 3.1.3 or later
• Restrict access to OAuth2 credential endpoints
• Monitor for suspicious activity on affected routes
• Implement additional logging and monitoring for OAuth2 credential endpoints
• Conduct a thorough review of existing OAuth2 credential configurations
• Update incident response plans to include potential OAuth2 credential endpoint exploitation
• Perform a vulnerability scan to identify any exposed Flowise deployments

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the affected versions and fixed version. The vendor advisory and release notes provide additional context on the vulnerability and mitigation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.