Skip to main content
VulnerabilityPublished

CVE-2026-133651: flowintel · Cross-Site Request Forgery

Affects flowintelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 4.1.0 when convenient.

Data as of 20 Nov 2026, 10:36 UTC

CVSS 4.0 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (CIRCL)CVSS 4.06.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
flowintelflowintelAffected
  • <4.1.0
Fixed in
  • 4.1.0
GitHubflowintelpkg:github/flowintelOther threatsAffected
  • <4.1.0
Fixed in
  • 4.1.0

CPE configurations (1)

  • cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade FlowIntel to version 4.1.0 or later, where this CSRF vulnerability has been fixed. No additional mitigation is required once the system is updated to the fixed version.

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. These routes accept HTTP GET requests, bypassing CSRF token validation which is only enforced on non-GET requests. An attacker can trick an authenticated user with editor or admin roles into triggering actions such as deletion or modification of cases, tasks, templates, connectors, icons, custom tags, taxonomies, and galaxies without the user's consent. This results in unauthorized data modification and loss of data integrity. The vulnerability is fixed in version 4.1.0.

References

Community reviews

Loading reviews…