CVE-2026-41947
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| dify | dify | {"endIncluding":"1.14.1"} | |
References
- https://github.com/langgenius/dify/commit/55d05fe52de880cd8497df8cea052351c594fad8
- https://github.com/langgenius/dify/pull/35793
- https://github.com/langgenius/dify/releases/tag/1.14.2
- https://huntr.com/bounties/a43076b2-fbc8-4750-9647-89a036b52f52
- https://www.vulncheck.com/advisories/dify-authorization-bypass-via-trace-configuration-endpoints
CWEs
CWE-639
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.