Skip to main content
VulnerabilityPublished

CVE-2026-133631: flowintel · Missing Authorization

Affects flowintelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 4.1.0 soon.

Data as of 20 Nov 2026, 09:35 UTC

CVSS 4.0 base score
7.1High
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.07.1
Patch
Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:L/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 vulnerabilities. Users should upgrade to version 4.1.0 or later to remediate the missing authorization checks, API endpoint access controls, and sensitive token exposure. Since this is a cloud service, the vendor manages remediation server-side; confirm with vendor advisory for deployment specifics. No additional mitigations are indicated beyond applying the official fix.

Description

FlowIntel versions prior to 4.1.0 contain multiple security vulnerabilities related to missing authorization checks, improper API endpoint access controls, and exposure of sensitive tokens. These flaws allow authenticated users to access private case data beyond their privileges, enable the chatbot API to invoke any API endpoint without restrictions, and expose sensitive tokens in system process tables to local users. The issues are fixed in version 4.1.0.

References

Community reviews

Loading reviews…