CVEs / CVE-2026-41947
CVE-2026-41947
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.
Affected products · 1
| Product | Versions affected | Fixed in |
|---|---|---|
| Dify | <= 1.14.1 | — |
Versions as NVD's CPE configuration states them; "—" means the record gives no fixed version, not that none exists. Check the vendor's advisory in the references.
In this registry
- Dify — agent dossier
References · 5
- github.com/langgenius/dify/commit/55d05fe52de880cd8497df8cea052351c594fad8
- github.com/langgenius/dify/pull/35793 — Issue Tracking, Mitigation, Patch
- github.com/langgenius/dify/releases/tag/1.14.2
- www.vulncheck.com/advisories/dify-authorization-bypass-via-trace-configuration-endpoints — Third Party Advisory
- www.zafran.io/resources/difytap-zafran-discovers-how-attackers-can-silently-wiretap-ai-dat
The official record's references, as NVD lists them, minus any tagged Exploit. Nothing here is an exploit or a proof of concept.
Description, scores, versions and references are the official CVE record's own, retrieved 2026-10-25 from NVD. Category, attack surface and cross-links are this registry's classification and can be wrong — use the button above. Not a severity assessment for your deployment.