CVE-2026-41950: langgenius dify · Insecure Direct Object Reference
Affects langgenius difySource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium : upgrade to 1.14.0 when convenient.
Data as of 2 Nov 2026, 22:58 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.14.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Upgrade langgenius/dify to 1.14.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| langgeniusdify | Affected
| Fixed in– |
GitHublanggenius/difypkg:github/langgenius/difyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict authenticated user permissions to minimize exposure and monitor for unusual file access patterns. Avoid sharing sensitive files within the affected versions. Upgrading to version 1.14.0 or later is implied but not confirmed as a fix; verify with vendor advisories.
Description
Dify before version 1.14.0 contains an authorization bypass vulnerability that allows authenticated users to read the full contents of files uploaded by other users within the same tenant by supplying an arbitrary file UUID in the files array of a chat-messages request. Attackers can exploit insufficient permission verification in the chat-messages endpoints to access files without ownership validation, bypassing workspace separation and signed URL protections to retrieve sensitive file contents through workflow processing.
References
- zafran.io/resources/difytap-zafran-discovers-how-attackers-can-silently-wiretap-ai-data-across-tenants-on-a-platform-powering-1m-apps (opens in a new tab)
- github.com/langgenius/dify/releases/tag/1.14.0 (opens in a new tab)
- huntr.com/bounties/181136ec-d957-4b75-8ea7-6fa7b8abd01d (opens in a new tab)
- vulncheck.com/advisories/dify-authorization-bypass-via-file-uuid (opens in a new tab)