CVE-2026-70478: FlowiseAI Flowise · Information Exposure
Affects FlowiseAI FlowiseSource CVE Database V5
Not known to be exploited · CVSS 9.2 Critical : upgrade to 3.1.2 as a priority.
Data as of 2 Nov 2026, 22:58 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.1.2, 3.1.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Upgrade Flowise to 3.1.2; flowiseai/Flowise to 3.1.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FlowiseAIFlowise | Affected
| Fixed in
|
GitHubflowiseai/Flowisepkg:github/flowiseai/FlowiseOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Flowise to version 3.1.3 or later, where this vulnerability is fixed by requiring proper authentication for the affected endpoint. No other mitigations are indicated by the vendor advisory.
Description
Flowise versions prior to 3.1.3 contain a vulnerability where the POST /api/v1/oauth2-credential/refresh/:credentialId endpoint is accessible without authentication. This endpoint decrypts stored OAuth credentials and returns refreshed access tokens, exposing sensitive information to unauthorized actors. An attacker with knowledge of a credential ID can obtain access tokens to connected services and potentially exhaust refresh-token quotas. The issue is fixed in version 3.1.3.