CVE-2026-52098: Flowise
Affects FlowiseSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 09:16 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | 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.
Description
Flowise version 3.1.2 contains a vulnerability that allows remote attackers to execute arbitrary code via the /api/v1/prediction/<flowId> endpoint. This issue enables unauthorized code execution on the affected system.
References
- nvd.nist.gov/vuln/detail/CVE-2026-52098 (opens in a new tab)
- github.com/FlowiseAI/Flowise (opens in a new tab)
- github.com/FlowiseAI/Flowise/blob/main/packages/server/src/utils/constants.ts (opens in a new tab)
- github.com/FlowiseAI/Flowise/blob/main/packages/server/src/utils/validateKey.ts (opens in a new tab)