CVE-2026-41950: CWE-639 Authorization Bypass Through User-Controlled Key in langgenius dify
Dify versions before 1.14.0 have an authorization bypass vulnerability (CVE-2026-41950) that allows authenticated users to read files uploaded by other users within the same tenant. This occurs due to insufficient permission checks on the chat-messages endpoint, enabling attackers to supply arbitrary file UUIDs and access sensitive file contents without proper ownership validation. The vulnerability bypasses workspace separation and signed URL protections. It has a medium severity with a CVSS 4.0 score of 6. No official patch or remediation guidance is currently available.
AI Analysis
Technical Summary
CVE-2026-41950 is an authorization bypass vulnerability in langgenius's dify product before version 1.14.0. Authenticated users can exploit insufficient permission verification in the chat-messages API endpoint by providing arbitrary file UUIDs in the files array of requests. This flaw allows them to read the full contents of files uploaded by other users within the same tenant, bypassing workspace separation and signed URL protections. The vulnerability is categorized under CWE-639 (Authorization Bypass Through User-Controlled Key). The CVSS 4.0 vector indicates network attack vector, low attack complexity, partial privileges required, no user interaction, and high impact on confidentiality.
Potential Impact
An attacker with authenticated access to dify can read sensitive files uploaded by other users in the same tenant without proper authorization. This compromises confidentiality by exposing potentially sensitive data across workspace boundaries. There is no indication of impact on integrity or availability. The vulnerability does not require user interaction and can be exploited remotely over the network.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict authenticated user permissions to the minimum necessary and monitor for unusual access patterns involving file UUIDs in chat-messages requests. Avoid sharing sensitive files in affected versions if possible.
CVE-2026-41950: CWE-639 Authorization Bypass Through User-Controlled Key in langgenius dify
Description
Dify versions before 1.14.0 have an authorization bypass vulnerability (CVE-2026-41950) that allows authenticated users to read files uploaded by other users within the same tenant. This occurs due to insufficient permission checks on the chat-messages endpoint, enabling attackers to supply arbitrary file UUIDs and access sensitive file contents without proper ownership validation. The vulnerability bypasses workspace separation and signed URL protections. It has a medium severity with a CVSS 4.0 score of 6. No official patch or remediation guidance is currently available.
CVSS v4.0
Score 6.0medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-41950 is an authorization bypass vulnerability in langgenius's dify product before version 1.14.0. Authenticated users can exploit insufficient permission verification in the chat-messages API endpoint by providing arbitrary file UUIDs in the files array of requests. This flaw allows them to read the full contents of files uploaded by other users within the same tenant, bypassing workspace separation and signed URL protections. The vulnerability is categorized under CWE-639 (Authorization Bypass Through User-Controlled Key). The CVSS 4.0 vector indicates network attack vector, low attack complexity, partial privileges required, no user interaction, and high impact on confidentiality.
Potential Impact
An attacker with authenticated access to dify can read sensitive files uploaded by other users in the same tenant without proper authorization. This compromises confidentiality by exposing potentially sensitive data across workspace boundaries. There is no indication of impact on integrity or availability. The vulnerability does not require user interaction and can be exploited remotely over the network.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, restrict authenticated user permissions to the minimum necessary and monitor for unusual access patterns involving file UUIDs in chat-messages requests. Avoid sharing sensitive files in affected versions if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-04-22T18:50:43.622Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69fa5868cbff5d861023d52b
Added to database: 5/5/2026, 8:51:52 PM
Last enriched: 5/13/2026, 3:52:58 AM
Last updated: 6/20/2026, 7:33:47 AM
Views: 120
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.