Security readout for executives and security teams
Plain-English summary
Dify versions before 1.14.0 may let a logged-in user read uploaded files belonging to other users in the same tenant. The risk is sensitive data disclosure through AI workflow processing, not system takeover. No provided source establishes active exploitation in the wild.
Executive priority
Treat this as a prompt patch for any Dify environment handling confidential documents. It is not described as unauthenticated or actively exploited, but confidentiality impact is high in shared AI workspaces.
Technical view
This is an object-level authorization failure, CWE-639, in Dify chat-messages endpoints. The files array can reference an arbitrary file UUID, and insufficient ownership checks allow workflow processing to retrieve full file contents despite signed URL protections.
Likely exposure
Organizations running langgenius Dify before 1.14.0 are most exposed, especially shared workspaces where multiple authenticated users upload or process sensitive files. Exposure requires authenticated access and a target file UUID.
Exploitation context
The source bundle includes technical advisories and exploit-labeled references, so practical exploitation appears documented. However, KEV is false and no provided source confirms active exploitation in the wild.
Researcher notes
Focus review on object authorization around file UUID resolution in chat-messages and workflow file retrieval. Validate ownership checks across tenant, workspace, and upload contexts without publishing operational exploit steps.
Mitigation direction
- Upgrade Dify to version 1.14.0 or later.
- Review the Dify 1.14.0 release notes for vendor fix details.
- Restrict Dify access to trusted authenticated users until upgraded.
- Review workspace file-handling permissions and tenant separation assumptions.
- Monitor for unusual chat workflow access involving uploaded files.
Validation and detection
- Inventory all Dify deployments and record running versions.
- Confirm no production instance remains below version 1.14.0.
- Review logs for unexpected file access through chat-messages workflows.
- Check whether sensitive uploads were processed in shared tenant workspaces.
- Validate vendor guidance against your deployment model.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-41950 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6VulnCheckCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6MediumVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.zafran.io/resources/difytap-zafran-discovers-how-attackers-can-silently-wiretap-ai-data-across-tenants-on-a-platform-powering-1m-appsCVE reference, VulnCheck · technical-description, exploit
- https://github.com/langgenius/dify/releases/tag/1.14.0CVE reference, VulnCheck · release-notes, patch
- https://huntr.com/bounties/181136ec-d957-4b75-8ea7-6fa7b8abd01dCVE reference, VulnCheck · technical-description, exploit
- https://www.vulncheck.com/advisories/dify-authorization-bypass-via-file-uuidCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.