Skip to main content
VulnerabilityPublished

CVE-2026-133661: flowintel · Missing Authorization

Affects flowintelSource CVE Database V5

0
Compare

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

Data as of 20 Nov 2026, 11:19 UTC

CVSS 4.0 base score
5.3Medium
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.05.3
Patch
Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/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

A fixed version 4.1.0 of FlowIntel is available that addresses these authorization and credential management vulnerabilities. Users should upgrade to version 4.1.0 or later to remediate these issues. No additional mitigation steps are indicated beyond applying the official fix.

Description

FlowIntel versions prior to 4.1.0 contain multiple authorization and credential management vulnerabilities. These flaws allow authenticated users to access connector instance metadata, case listings, and templates without proper permission checks, potentially exposing sensitive configuration and credentials. Additionally, editing connector instances can reuse API keys without re-authentication, and outbound MISP connector keys can be misused for inbound alert authentication, leading to credential confusion. These issues collectively enable unauthorized data access and credential misuse.

References

Community reviews

Loading reviews…