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.
Published: 2026-10-05
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Improper Access Control that allows authenticated users to modify other applications' server settings
Action: Immediate Patch
AI Analysis

Impact

The vulnerability is an IDOR in the PUT /console/api/apps/<app_id>/server endpoint of Dify. It allows an authenticated workspace member to provide a server ID that belongs to a different application, retrieve that server, and change its status or parameters. This can redirect data flows or disable the MCP service for other applications, potentially compromising integrity and availability.

Affected Systems

Affected is the langgenius:dify platform. Any deployment using a Dify version earlier than 1.16.0 is vulnerable. Version 1.16.0 and later contain the fix.

Risk and Exploitability

With a CVSS score of 7.1, the vulnerability is considered moderate to high severity. The EPSS score is not reported, and the vulnerability is not listed in the CISA KEV catalog, suggesting no known widespread exploitation. The likely attack vector is internal, requiring authentication as a workspace member within the same tenant. Exploitation would involve constructing a request to the PUT endpoint with a server ID from another application to alter its configuration.

Generated by OpenCVE AI on October 6, 2026 at 00:25 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Dify version 1.16.0 or newer to apply the fix
  • Verify that the server ID supplied in the PUT request matches the application and tenant of the authenticated user
  • Deploy access‑control checks around the /console/api/apps/<app_id>/server endpoint to prevent cross‑application updates

Generated by OpenCVE AI on October 6, 2026 at 00:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 06 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Tue, 06 Oct 2026 00:45:00 +0000

Type Values Removed Values Added
First Time appeared Langgenius
Langgenius dify
Vendors & Products Langgenius
Langgenius dify

Mon, 05 Oct 2026 23:15:00 +0000

Type Values Removed Values Added
Description Dify is an open-source LLM app development platform. Prior to 1.16.0, the PUT /console/api/apps/&lt;app_id&gt;/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.
Title Dify: IDOR in AppMCPServer PUT Endpoint Allows Modification of Other Apps' MCP Servers
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L'}

Subscriptions

Langgenius Dify
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-06T14:47:53.059Z

Reserved: 2026-10-05T19:11:07.948Z

Link: CVE-2026-105761

cve-icon Vulnrichment

Updated: 2026-10-06T14:35:28.340Z

cve-icon NVD

Status : Deferred

Published: 2026-10-05T23:17:03.050

Modified: 2026-10-06T16:08:43.180

Link: CVE-2026-105761

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-06T00:30:18Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key