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

Agent app platform · Apache-2.0 · GitHub; self-hosted/cloud

Dify

Very large low-code agent/RAG platform with broad deployment footprint. Publisher: LangGenius. Also ranked in Technology & Software Engineering (#32), Business & Enterprise Operations (#34), Supply Chain, Manufacturing & Logistics (#60).

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 · 3 vendor-level records (inherited)T5

Security39 CVEs linked in the registry · 15 critical/high · newest 2026-10-06linked

ProtocolsModel Context Protocol (MCP) claimed — named in the resource's own tags; no endpoint at the publisher's well-known paths sourceAgent2Agent (A2A) probed, not foundAgentic Resource Discovery (ARD) probed, not found1 / 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 LangGenius 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 LangGenius, 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 Dify 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

39 linked · the registry

CVE-2026-105762

2026-10-06

Dify is an open-source LLM app development platform. Prior to 1.13.0, the /console/api/remote-files/upload endpoint in api/controllers/web/remote_files.py accepted an attacker-con…

Auth bypass · SSRF · unreviewed

High 8.3

CVE-2026-105761

2026-10-05

Dify is an open-source LLM app development platform. Prior to 1.16.0, the PUT /console/api/apps/<app_id>/server endpoint in api/controllers/console/app/mcp_server.py used Ap…

Auth bypass · unreviewed

High 7.1

CVE-2026-85021

2026-09-03

A vulnerability was determined in langgenius dify 1.13.0. Affected is the function router.replace of the file web/app/(shareLayout)/components/splash.tsx of the component Splash L…

Code execution · unreviewed

Low 2.1

CVE-2026-85022

2026-09-03

A vulnerability was identified in langgenius dify 1.13.0. Affected by this vulnerability is the function router.replace of the file web/app/(shareLayout)/webapp-signin/components/…

Code execution · unreviewed

Low 2.0

CVE-2026-18632

2026-08-03

A security flaw has been discovered in langgenius dify up to 1.14.2. This issue affects the function jinja2.Template of the file api/core/helper/code_executor/jinja2/jinja2_transf…

Code execution · unreviewed

Low 2.1

CVE-2026-18266

2026-07-29

Dify AI Workflow oauth_redirect_url Open Redirect Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Dify. Us…

Data exfiltration · unreviewed

Medium 5.4

CVE-2026-61461

2026-07-10

Dify before 1.16.0-rc1 contains a SQL injection vulnerability in the MyScale vector store backend that allows attackers to execute arbitrary SQL by supplying unsanitized search pa…

— · fix known · unreviewed

High 8.7

CVE-2026-41947

2026-05-18

Dify before version 1.14.2 contains an authorization bypass vulnerability that allows authenticated editor users to set and enable trace configurations for any application regardl…

Auth bypass · fix known · unreviewed

Critical 9.3

31 more · All 39 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

–

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

3 records 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

○

ISO 27001 · ISO 27001

T4 Vendor-claimed · vendor-level

Vendor-claimed

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

re-check 2026-11-02

○

SOC 2 · SOC 2 Type II

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-10-23

dify: v1.18.0 — Smarter Agent Routing, Portable Apps, Deeper Workflow Visibility

GitHub releases · Dify 1.18.0 brings **Agents that route workflows**, **portable app packages**, **deeper visibility into nested workflow runs**, and the opt-in **Agent Knowledge Base** experience. OpenAPI and the new difyctl expand how you build and manage

Product update

2026-09-10

dify: v1.17.1 - Bug Fixes and Improvements

GitHub releases · > [!WARNING] > **Self-hosted deployments using the bundled Weaviate must complete a manual, staged upgrade before starting 1.17.1.** The bundled Weaviate server moves from `1.27.0` to `1.39.2` — 12 minor versions — and skipping minors **is

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 · #16 of 100 in the curated list

Adoption / usage30 / 30

Trust & security17 / 25

Project / product health19 / 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 (3)

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

ISO 27001 — vendor-claimed, vendor-level source

SOC 2 Type II — vendor-claimed, vendor-level source

Unknowns to check (5)

Your lawful basis and DPIA for PHI and personal data the agent will touch

That the SOC 2 report period covers the components you will use; request the report under NDA

Whether the ISO 27001 certificate scope names this service, or only the platform

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

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

Suggested restrictions for a pilot (1)

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_f87a792228998616

Open the full record (JSON) →