# CVE-2026-105761: Dify: IDOR in AppMCPServer PUT Endpoint Allows Modification of Other Apps' MCP Servers

> An authenticated user can modify other applications' MCP server configurations due to missing ownership checks, potentially redirecting data or disabling services.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **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 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-ccrj-frp2-c945

## What is CVE-2026-105761?

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

### Official description

Dify is an open-source LLM app development platform. Prior to 1.16.0, the PUT /console/api/apps/<app_id>/server endpoint in api/controllers/console/app/mcp_server.py used AppMCPServerController.put() to retrieve an AppMCPServer by the client-supplied server ID without verifying that the server belonged to the requested application and tenant. An authenticated workspace member could therefore change another application's MCP server status and parameters, potentially redirecting data or disabling the service. This issue is fixed in version 1.16.0.

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

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


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

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

## Is CVE-2026-105761 being exploited?

There is no known exploitation of CVE-2026-105761 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105761 is a high-severity missing authorization vulnerability in langgenius dify, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105761 in the wild and no public exploit code.

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-105761/ (Markdown: https://insights.sbomify.com/CVE-2026-105761/index.md)
```

## Sources

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

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