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 regardless of tenant ownership. Attackers can exploit missing tenant ownership checks in the trace configuration endpoints to redirect all messages and responses from victim applications to attacker-controlled LLM trace providers. NOTE: Dify Cloud allows unauthenticated free self-registration, making account creation trivially accessible to any attacker.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/langgenius/dify/pull/35793 Issue Tracking, Mitigation, Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.3 · difyNVD modified 2026-10-14 20:10
Affected (CPE criteria) 1
cpe:2.3:a:dify:dify:*:*:*:*:*:*:*:*
References 6
- https://github.com/langgenius/dify/commit/55d05fe52de880cd8497df8cea052351c594fad8
- https://github.com/langgenius/dify/pull/35793 Issue Tracking, Mitigation, Patch
- https://github.com/langgenius/dify/releases/tag/1.14.2
- https://huntr.com/bounties/a43076b2-fbc8-4750-9647-89a036b52f52 Exploit, Third Party Advisory
- https://www.vulncheck.com/advisories/dify-authorization-bypass-via-trace-configuration-endpoints Third Party Advisory
- https://www.zafran.io/resources/difytap-zafran-discovers-how-attackers-can-silently-wiretap-ai-data-across-tenants-on-a-platform-powering-1m-apps