PatchSiren cyber security CVE debrief
CVE-2026-70478 FlowiseAI CVE debrief
CVE-2026-70478 Flowise OAuth2 Credential Refresh Endpoint Vulnerability. Flowise, a drag & drop user interface to build customized large language model flows, has a critical vulnerability in its OAuth2 credential refresh endpoint. The endpoint, which requires no authentication, can decrypt stored credentials and send refresh requests to the configured OAuth provider. This issue allows an attacker with a credential ID to access the victim's connected service and exhaust refresh-token quotas. Defenders and administrators of Flowise instances should assess exposure and prioritize remediation to prevent unauthorized access and quota exhaustion.
- Vendor
- FlowiseAI
- Product
- Flowise
- CVSS
- CRITICAL 9.2
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-04
- Original CVE updated
- 2026-09-11
- Advisory published
- 2026-08-04
- Advisory updated
- 2026-09-11
Who should care
Defenders and administrators of Flowise instances should assess exposure and prioritize remediation. This vulnerability can be used to access connected services and exhaust refresh-token quotas.
Why it matters
CVE-2026-70478 is a critical vulnerability in Flowise's OAuth2 credential refresh endpoint. Defenders and administrators of Flowise instances should assess exposure and prioritize remediation to prevent unauthorized access to connected services and exhaustion of refresh-token quotas.
- An attacker with a credential ID can access the victim's connected service
- An attacker can exhaust refresh-token quota
- Remediation priority is high due to the critical CVSS score of 9.2
Technical summary
Flowise, a drag & drop user interface to build customized large language model flows, has a critical vulnerability in its OAuth2 credential refresh endpoint. Prior to version 3.1.3, the POST /api/v1/oauth2-credential/refresh/:credentialId endpoint requires no authentication. An attacker can use this endpoint to decrypt stored credentials and send refresh requests to the configured OAuth provider, potentially gaining access to connected services and exhausting refresh-token quotas. This issue is fixed in version 3.1.3.
Defensive priority
High
Recommended defensive actions
- Review and update Flowise to version 3.1.3 or later
- Restrict access to the affected endpoint
- Monitor for suspicious activity on the OAuth provider
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record and NVD entry provide details on the vulnerability in Flowise's OAuth2 credential refresh endpoint. The endpoint requires no authentication and can be used to decrypt stored credentials and send refresh requests to the configured OAuth provider. Evidence is limited to public CVE and NVD information. Defenders should verify Flowise instance exposure and review official advisories for specific guidance.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-70478 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-70478
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-70478 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-70478
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-qgvm-j2hm-6m38
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.