Data & Analytics Top 100 / #52ARD = Agentic Resource Discovery · A2A = Agent2Agent · MCP = Model Context Protocol

Visual agent builder · Apache-2.0 · GitHub; cloud/self-hosted

Flowise

Popular drag-and-drop LLM/agent workflow builder. Publisher: FlowiseAI. Also ranked in Technology & Software Engineering (#92).

Vendor page ↗+ CompareExport JSON

Trust profileas of 2026-10-26

Publisherlikely · Repository ownership or inferred publisher domain — repository or Hub account ownershiplikely

Complianceno evidence about this agent · 1 vendor-level record (inherited)T5

Security150 CVEs linked in the registry · 120 critical/high · newest 2026-09-26linked

ProtocolsModel Context Protocol (MCP) probed, not foundAgent2Agent (A2A) probed, not foundAgentic Resource Discovery (ARD) probed, not found0 / 3

TracesNone found — nobody has published what this agent does under attacknone

Issues found0 regulator actions · 0 incidents · 0 withdrawn certificates · CVEs: see Securitylinks only

Publisher unconfirmed: the evidence below is shown but not counted in the governance score, because nothing yet ties this listing to FlowiseAI beyond repository or Hub account ownership. A vendor-domain page, marketplace listing, ARD manifest or A2A card would confirm it.

Evidence available — not a safety certification. Suitability depends on your task, deployment and permissions. Rows marked vendor-level describe FlowiseAI, not this agent specifically.

Traces — under attack, in defence, in incidents

none public · what a trace is

No public trace found. Nobody has published what Flowise does when its inputs carry instructions it should not follow, when a tool asks for credentials, or when a task invites a destructive command. Defenders can't learn from what they can't see: run it in a sandbox before the pilot and keep the transcript, or ask the vendor to publish one.

● third-party or vendor report · ◎ this registry's own probe transcript · ⚠ data left the environment. A trace describes one version on one date; it is evidence of behaviour, never a certification. Rows marked unreviewed have not yet been checked against their source by the maintainer.

CVEs — on the official record

150 linked · the registry

CVE-2026-100605

2026-09-26

Flowise through 3.1.4 contains missing route-level RBAC checks on chat message endpoints that allow low-privileged API keys to read and delete chat history. Attackers with valid b…

Credential access · Auth bypass · unreviewed

High 7.5

CVE-2026-100606

2026-09-26

Flowise through 3.1.4 (Enterprise/platform mode with SSO enabled) contains an authentication bypass in the SSO login path. When an SSO callback arrives with an email matching a us…

Auth bypass · unreviewed

Critical 9.2

CVE-2026-100607

2026-09-26

Flowise through 3.1.4 resolves SSO and local-password users solely by email without storing provider or subject identifier bindings, allowing attackers to authenticate as any exis…

Credential access · Auth bypass · unreviewed

Critical 9.2

CVE-2026-100608

2026-09-26

Flowise through 3.1.4 does not enforce authorization on the BullMQ admin dashboard. When the server runs in queue mode with the dashboard enabled and not in cloud mode (MODE=queue…

Credential access · Auth bypass · unreviewed

High 8.7

CVE-2026-100609

2026-09-26

Flowise (npm packages `flowise` and `flowise-components`) through 3.1.4 looks up credentials by ID without filtering on the requesting user's workspace (findOneBy({ id: credential…

Credential access · Auth bypass · unreviewed

High 7.6

CVE-2026-100610

2026-09-26

Flowise through 3.1.4 exposes GET /api/v1/upsert-history/:id and PATCH /api/v1/upsert-history without route-level permission checks, and the backing service performs no workspace…

Credential access · Auth bypass · unreviewed

High 7.7

CVE-2026-91929

2026-09-15

Flowise versions before 3.1.4 contain cross-tenant authorization gaps in Enterprise endpoints that fail to verify resource ownership before operations. Attackers with Enterprise a…

Credential access · Auth bypass · unreviewed

High 7.6

CVE-2026-91930

2026-09-15

Flowise before 3.1.4 fails to scope enterprise organization and workspace membership APIs to the caller's tenant, allowing authenticated users to supply arbitrary organization IDs…

Privilege escalation · unreviewed

High 7.7

142 more · All 150 in the registry → Severity is the official record's; nothing here enters the score. Links are by listed product, so a CVE that names a different component of the same platform may be missing.

Compliance evidence

Jurisdiction: EU · 6 frameworks shown

–

SOC 2

T5 Unknown

Nothing found in the sources checked.

Scope: — · registries, marketplaces, vendor pages

ask the vendor

–

ISO 27001

T5 Unknown

Nothing found in the sources checked.

Scope: — · registries, marketplaces, vendor pages

ask the vendor

–

ISO 27701

T5 Unknown

Nothing found in the sources checked.

Scope: — · registries, marketplaces, vendor pages

ask the vendor

–

ISO 42001

T5 Unknown

Nothing found in the sources checked.

Scope: — · registries, marketplaces, vendor pages

ask the vendor

–

CSA STAR

T5 Unknown

Nothing found in the sources checked.

Scope: — · CSA STAR Registry

ask the vendor

"Unknown" means nothing was found in the sources checked — registries, marketplaces and the vendor's own pages. It is not a finding of non-compliance; ask the vendor.

About the vendor — inherited, not agent-specific

1 record matched at organisation level

○

GDPR · DPA available

T4 Vendor-claimed · vendor-level

Vendor-claimed

Scope: entity · vendor page · 2026-10-26

re-check 2026-11-02

A vendor-level registry entry proves the organisation was assessed; whether this agent is inside that scope is a question for the vendor. These rows do not count toward the agent's evidence tier.

✔ found · ○ claimed · – not found · ⚠ expired, stale or revoked. Every row links to its source.Dispute or correct this dossier

GDPR, assembled from checks

GDPR● 0 found in registries or documents○ 1 vendor-claimed⚠ 0 issues linkedas of 2026-10-26

○ ClaimedDPA available: Vendor-claimed (vendor page, 2026-10-26). A DPA is a contract you still have to sign and review.

– Not foundNo Article 42 GDPR seal. "GDPR certified" is never shown without one.

☐ You checkYour lawful basis, DPIA, and whether this agent is inside the certificate scope.

News and chatter

last 90 days · linked with confidence ≥ 0.85

2026-07-29

Flowise release 3.1.4

GitHub releases · ## What's Changed * Fix Type Validation For Session ID by @yau-wd in https://github.com/FlowiseAI/Flowise/pull/6568 * Fix Flowise 709 Make Custom MCP stdio command allowlist operator-controlled by @yau-wd in https://github.com/FlowiseAI/F

Product update

Headline, link and a summary attributed to the outlet. News never changes trust or domain scores.

Data & Analytics score

data profile · sar-score-2.0 · #52 of 100 in the curated list

Adoption / usage25 / 30

Trust & security16 / 25

Project / product health20 / 20

Ecosystem / interoperability14 / 15

Domain expertise / fit99 / 100

Governance / compliance evidence0 / 100

Docs / transparency9 / 10

Raw component / maximum, then weighted by the data profile (adoption 25, trust 20, project 20, ecosystem 15, domain 15, governance 0, docs 5). Trust and governance are computed from the evidence on this page (vendor-level rows at half credit); the other components come from the curated workbook, whose order is the rank. Unknown components count as 0 and are never imputed.

Before you deploy

Derived from the evidence ledger. This agent is not yet in the reference set, so deployment questions (credentials, approval, data handling) are not answered here — ask the vendor.

Evidence supporting this use (1)

GDPR DPA available — vendor-claimed, vendor-level source

Unknowns to check (3)

The transfer mechanism you will rely on; DPF covers EU-to-US transfers only

Ask the vendor for SOC 2, ISO 27001, ISO 27701, ISO 42001, CSA STAR evidence; none was found in the sources checked

Whether the agent exposes MCP or A2A endpoints; none were observed

Suggested restrictions for a pilot (2)

Ask for the SOC 2 report under NDA before the pilot touches customer data; none was found in the sources checked.

No public trace of this agent under adversarial input was found. Run it in a sandbox against your own prompt-injection and tool-abuse scenarios before the pilot, and keep the transcript; the enterprise edition records one.

Rules: config/deploy_rules.json. Advice for a bounded pilot, not a verdict.

Provenance

seed workbookscores, rank, category

vendor pageclaims

Hacker News, GDELT, vendor feedsnews and chatter

First seen2026-10-26

Recordres_189936a4dd7b2a51

Open the full record (JSON) →