# CVE-2026-41950: Dify < 1.14.0 Authorization Bypass via File UUID

> Authenticated users can read other users' files in the same tenant by exploiting missing ownership validation in chat message endpoints.

- **Severity:** Medium 6.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:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-r2m5-9rwx-269r

## What is CVE-2026-41950?

CVE-2026-41950 is a medium-severity missing authorization vulnerability in langgenius dify, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-41950?

It affects 1 product.


Products: Langgenius Dify.

## How do I fix CVE-2026-41950?

No fix has been published for CVE-2026-41950 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41950 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41950 exists.

## Other vulnerabilities in langgenius dify

- [CVE-2025-56157](https://insights.sbomify.com/CVE-2025-56157/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-3466](https://insights.sbomify.com/CVE-2025-3466/): Unsanitized Input in langgenius/dify (critical 9.8)
- [CVE-2025-63386](https://insights.sbomify.com/CVE-2025-63386/): Misconfiguration in n/a (critical 9.1)
- [CVE-2025-63388](https://insights.sbomify.com/CVE-2025-63388/): Misconfiguration in n/a (critical 9.1)
- [CVE-2024-10252](https://insights.sbomify.com/CVE-2024-10252/): Code Injection in langgenius/dify (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41950 and fix it if it is affected.

What it is: CVE-2026-41950 is a medium-severity missing authorization vulnerability in langgenius dify, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41950 exists.

Affected product: langgenius dify. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41950/ (Markdown: https://insights.sbomify.com/CVE-2026-41950/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41950
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41950
- OSV: https://osv.dev/vulnerability/CVE-2026-41950

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41950/
Summaries are generated and may contain mistakes; the official description above is the record.