FlowIntel contained a Cross-Site Request Forgery (CSRF) vulnerability affecting fourteen web routes that performed
Source GCVE Database
Not known to be exploited · CVSS 6.1 Medium : upgrade to 4.1.0 when convenient.
Data as of 20 Nov 2026, 13:50 UTC
Thin evidence
One scorer or none| CNA (CIRCL) | CVSS 4.0 | 6.1 |
|---|
- Patch
- Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 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 19 Nov 2026.
What to do
Upgrade flowintel to 4.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| flowintelflowintel | Affected
| Fixed in
|
GitHubflowintelpkg:github/flowintelOther 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
A fix is available in FlowIntel version 4.1.0 and later. Users should upgrade to version 4.1.0 or newer to remediate this vulnerability. Until upgraded, avoid clicking on untrusted links while authenticated and consider restricting access to affected routes to POST requests only, ensuring proper CSRF token validation. No vendor advisory content was provided to indicate otherwise.
Description
FlowIntel versions prior to 4.1.0 contain a Cross-Site Request Forgery (CSRF) vulnerability affecting fourteen web routes that perform destructive or state-changing operations. The vulnerability arises because these routes accept HTTP GET requests, which bypass Flask-WTF CSRF token validation that only applies to non-GET requests. An attacker can exploit this by tricking an authenticated user with editor or admin roles into visiting a crafted link or page, causing unauthorized deletion or modification of cases, tasks, templates, connectors, icons, custom tags, taxonomies, and galaxies. This results in loss of data integrity without requiring special privileges beyond a valid authenticated session.