Skip to content

AAK-MCP-DIFY-CVE-2026-105761-001: Dify below 1.16.0: a workspace member can change another app's MCP server

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/container_image_pins.py
Auto-fixable
No.
SARIF name
DifyMcpServerCrossAppUpdate

What it detects

Dify (langgenius/dify), a self-hosted LLM app platform, can publish an app as an MCP server. Before 1.16.0, PUT /console/api/apps/<app_id>/server loaded the AppMCPServer by the server id the client sent, without checking that it belonged to the requested app and tenant, so an authenticated workspace member could change another app's MCP server status and parameters, redirecting its data or switching it off (CVE-2026-105761, CVSS 3.1 7.1, CWE-639, GHSA-ccrj-frp2-c945). The server ships as the Docker Hub image langgenius/dify-api, which Dify's compose file pins by version. 1.16.0 looks the server up by its app and tenant (fix commit 62cb5b5).

How to fix

Upgrade the langgenius/dify-api image to 1.16.0 or later and pin its tag.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-DIFY-CVE-2026-105761-001

Limitations

Reads langgenius/dify-api image references below 1.16.0 in compose files, Kubernetes manifests, Helm values, Dockerfiles and MCP configs. The bare Docker Hub name is matched, so docker.io/langgenius/dify-api is not read. latest was 1.17.1 on 2026-10-06, so an untagged reference is not reported. A source checkout run without the image states no version AAK reads, and langgenius/dify-web is not pinned because the endpoint is in the API server.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-DIFY-CVE-2026-105761-001.md: the page then shows that text, with the registry reference appended under it.