Security readout for executives and security teams
Plain-English summary
Dify versions before 1.14.2 could let a user read previews of documents they do not own if they know a file UUID. In multi-tenant or shared workspace deployments, this can expose sensitive uploaded content across boundaries. The provided sources do not show confirmed active exploitation.
Executive priority
Treat as urgent for any Dify environment containing sensitive customer, internal, or regulated documents. Prioritize upgrade and exposure review before broader operational work.
Technical view
The flaw is an authorization bypass in Dify's file preview endpoint. Ownership or workspace permission checks were missing, allowing document preview disclosure of up to 3,000 characters by file UUID. The CVE maps to CWE-639 and is fixed in the 1.14.2 release and linked patch.
Likely exposure
Exposed Dify deployments before 1.14.2 are the concern, especially multi-tenant, workspace-based, or cloud/self-registration environments handling confidential uploaded documents.
Exploitation context
Provided sources describe exploitability when an attacker has or intercepts a file UUID. KEV is false, and the bundle provides no evidence of active exploitation in the wild.
Researcher notes
Evidence supports an IDOR-style tenant boundary failure in file preview handling. Scope should focus on pre-1.14.2 deployments, file UUID exposure paths, and whether audit logs can distinguish legitimate preview activity from cross-workspace access.
Mitigation direction
- Upgrade Dify to version 1.14.2 or later.
- Review the linked Dify patch and release notes for vendor guidance.
- Restrict Dify access until upgraded, especially public or self-registration deployments.
- Review document exposure risk for sensitive uploads.
- Monitor preview endpoint access for unexpected users or tenants.
Validation and detection
- Inventory Dify instances and confirm their running versions.
- Identify whether public registration or broad authenticated access is enabled.
- Review logs for unusual file preview access across workspaces or tenants.
- Confirm authorization tests cover file preview access boundaries.
- Verify the deployed code includes the linked authorization fix.
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 lookupCVE-2026-41949 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
- High
- CVSS
- 8.2 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N2.23.6VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.2HighVector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/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://huntr.com/bounties/d50a0240-7951-4939-b989-9bded66c7682CVE reference, VulnCheck · technical-description, exploit
- https://github.com/langgenius/dify/releases/tag/1.14.2CVE reference, VulnCheck · release-notes
- https://github.com/langgenius/dify/pull/35797CVE reference, VulnCheck · issue-tracking
- https://github.com/langgenius/dify/commit/432a6412a3fdb30ce48003d699b90cc7d890df20CVE reference, VulnCheck · patch
- https://www.vulncheck.com/advisories/dify-authorization-bypass-via-file-preview-endpointCVE 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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.