Unauthenticated OAuth token rotation via prefix-matched refresh route
Published Aug 6, 2026 · Updated Aug 6, 2026
Authentication bypass in Flowise 3.1.4 and earlier allows remote attackers to rotate stored OAuth tokens via a credential identifier. Prefix matching in WHITELIST_URLS treats the identifier-suffixed refresh route as exempt, while the handler loads credentials by ID without workspace checks. Knowledge of a valid credential identifier is required; exploitation changes another workspace's token state and can interrupt dependent OAuth integrations.
Summary
What happened
Authentication bypass in Flowise 3.1.4 and earlier allows remote attackers to rotate stored OAuth tokens via a credential identifier. Prefix matching in WHITELIST_URLS treats the identifier-suffixed refresh route as exempt, while the handler loads credentials by ID without workspace checks. Knowledge of a valid credential identifier is required; exploitation changes another workspace's token state and can interrupt dependent OAuth integrations.
The record
- CVE
- CVE-2026-70636
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-862, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.1.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- CayCon unauthenticated OAuth refresh reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo