# CVE-2026-105761: Dify authorization bypass in MCP server endpoint

Source: https://junglewise.ai/threats/cve-2026-105761-dify-is-an-open-source-llm-app-development-platform-prior-to-1  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-05. Updated: 2026-10-05  
License: CC BY 4.0 with a link back

CVE-2026-105761 · Severity: high · CVSS 7.1 · Published 2026-10-05

Dify is an open-source platform for building applications powered by large language models. A flaw in version prior to 1.16.0 allows authenticated workspace members to modify MCP server configurations belonging to other applications within the same tenant, potentially redirecting data or disabling critical services used by those applications.

Technologies: [Langgenius Dify](https://junglewise.ai/threats/technologies/dify). Vendors: [Langgenius](https://junglewise.ai/threats/vendors/langgenius).

## Quick answers

**Is CVE-2026-105761 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-105761 being exploited in the wild.

**How severe is CVE-2026-105761?** High severity, with a CVSS score of 7.1, published 5 October 2026.

**Which products and versions are affected?** Langgenius Dify prior to 1.16.0.

**Is there a fix for CVE-2026-105761?** Yes: fixed in 1.16.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-105761 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-105761?** Check whether you run Langgenius Dify at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 1.16.0

## Technical details

The PUT /console/api/apps/<app_id>/server endpoint in AppMCPServerController.put() retrieves AppMCPServer resources by client-supplied server ID without verifying ownership against the requested application and tenant. An authenticated workspace member can exploit this to change MCP server status and parameters across application boundaries within a shared tenant.

## Affected products

- langgenius Dify prior to 1.16.0

## Timeline

- 2026-10-05: advisory

## References

- [https://github.com/langgenius/dify/commit/62cb5b586504b730731e28e743c038b72950058e](https://github.com/langgenius/dify/commit/62cb5b586504b730731e28e743c038b72950058e)
- [https://github.com/langgenius/dify/pull/38177](https://github.com/langgenius/dify/pull/38177)

## Related threats

- [langgenius dify hard-coded credentials in sandbox](https://junglewise.ai/threats/cve-2026-123135-a-vulnerability-was-found-in-langgenius-dify-up-to-1-18-0-2-0-0)
- [langgenius dify DOM-based XSS in redirect URL handler](https://junglewise.ai/threats/cve-2026-85022-langgenius-dify-dom-based-xss-in-redirect-url-handler)
- [langgenius Dify DOM-based XSS in splash.tsx redirect](https://junglewise.ai/threats/cve-2026-85021-langgenius-dify-dom-based-xss-in-splash-tsx-redirect)
- [LangGenius Dify server-side template injection in Jinja2 handler](https://junglewise.ai/threats/cve-2026-18632-langgenius-dify-server-side-template-injection-in-jinja2-handler)
- [LangGenius Dify open redirect in AppInitializer OAuth flow](https://junglewise.ai/threats/cve-2026-18266-langgenius-dify-open-redirect-in-appinitializer-oauth-flow)