OAuth token theft via unauthenticated refresh route
Published Aug 4, 2026 · Updated Aug 4, 2026
Information disclosure in Flowise 3.1.2 and earlier allows remote attackers to obtain OAuth access tokens via a refresh request. The whitelisted POST /api/v1/oauth2-credential/refresh/:credentialId route decrypts the stored OAuth credential and returns the provider's refreshed access_token without authenticating the caller. Exploitation requires a valid credential ID and grants access to its connected service; repeated requests can also exhaust the refresh-token quota.
Summary
What happened
Information disclosure in Flowise 3.1.2 and earlier allows remote attackers to obtain OAuth access tokens via a refresh request. The whitelisted POST /api/v1/oauth2-credential/refresh/:credentialId route decrypts the stored OAuth credential and returns the provider's refreshed access_token without authenticating the caller. Exploitation requires a valid credential ID and grants access to its connected service; repeated requests can also exhaust the refresh-token quota.
The record
- CVE
- CVE-2026-70478
- Published
- Aug 4, 2026
- Updated
- Aug 4, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-200, T1528
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 4, 2026CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=< 3.1.2
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.
Weakness, pattern, technique
Public exploit references
- GHSA-qgvm-j2hm-6m38 proof of conceptproof 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