CVE-2026-41947 json
Dify < 1.14.2 Authorization Bypass via Trace Configuration Endpoints
published 5mo ago modified yesterday also EUVD-2026-30772
- cvss
- 9.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.0%
- EPSS 6.0% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- langgenius dify 1.14.2
- github.com/langgenius/dify@55d05fe commit
- github.com/langgenius/dify#35793 pull request
- github.com/langgenius/dify/releases/tag/1.14.2 release
Is CVE-2026-41947 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 5mo ago
Exploit prediction
5.97% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- zafran.io https://www.zafran.io/resources/difytap-zafran-discovers-how-attackers-can-silently-wiretap-ai-data-across-tenants-on-a-platform-powering-1m-apps referenced PoC, tagged "exploit" by a source, unverified
- huntr.com https://huntr.com/bounties/a43076b2-fbc8-4750-9647-89a036b52f52 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| CNA | 4.0 | 9.3 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- langgenius dify
Classification
- Weakness
-
- CWE-639 Authorization Bypass Through User-Controlled Key
References
-
github.com
/langgenius/dify/pull/35793
issue-tracking, patch, mitigation
-
github.com
/langgenius/dify/commit/55d05fe52de880cd8497df8cea052351c594fad8
patch
-
zafran.io
/resources/difytap-zafran-discovers-how-attackers-can-silently-wiretap-ai-data-across-tenants-on-a-platform-po
technical-description, exploit
-
huntr.com
/bounties/a43076b2-fbc8-4750-9647-89a036b52f52
technical-description, exploit, third-party-advisory
-
github.com
/langgenius/dify/releases/tag/1.14.2
release-notes
-
vulncheck.com
/advisories/dify-authorization-bypass-via-trace-configuration-endpoints
third-party-advisory
Sources
- CVE List CVE-2026-41947
- NVD CVE-2026-41947
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.