CVE-2026-58141

Dify version 1.14.1 and prior contain a path traversal vulnerability that allows authenticated users to manipulate requests forwarded to the Plugin Daemon's internal REST API. Attackers can exploit insufficient URL path sanitization to access internal endpoints.

Dify before version 1.14.2 contains an authorization bypass vulnerability that allows authenticated editor users to set and enable trace configurations for any application regardless of tenant ownership. This vulnerability allows attackers to redirect all messages and responses from victim applications to attacker-controlled LLM trace providers.

Dify 1.9.1 and 1.17.0 expose the /console/api/system-features endpoint to unauthenticated HTTP GET requests, returning system feature and configuration information. Per the maintainer, the endpoint is unauthenticated by design as a bootstrap mechanism for dashboard initialization, and the data is non-sensitive with no PII, credentials, or secrets exposed.

Dify up to version 1.5.1 includes default PostgreSQL credentials (username and password) in its docker-compose.yaml file. The vendor reports that PostgreSQL is not exposed on TCP port 5432 by default since version 1.0.1.

CORS misconfiguration vulnerability in Dify v1.9.1 in the /console/api/system-features endpoint. The endpoint reflects arbitrary Origin headers and sets Access-Control-Allow-Credentials: true, allowing any external domain to make authenticated cross-origin requests. NOTE: The supplier disputes this, arguing that credentialed requests do not provide additional access compared to unauthenticated requests.

Dify is an open-source LLM app development platform. Prior to 1.13.0, the /console/api/remote-files/upload endpoint in api/controllers/web/remote_files.py accepted an attacker-controlled URL without authentication and caused the Dify server to retrieve it. A remote attacker could use the endpoint to send requests to internal services or cloud metadata endpoints, potentially exposing sensitive data and using the server as a network pivot. This issue is fixed in version 1.13.0.

Dify, an open-source LLM app development platform, prior to 1.16.0, in the PUT /console/api/apps/<app_id>/server endpoint, did not verify that the MCP server belonged to the requested application and tenant. An authenticated workspace member could change another application's MCP server status and parameters, potentially redirecting data or disabling the service.

A security flaw in langgenius dify up to 1.14.2, affecting the jinja2.Template function in api/core/helper/code_executor/jinja2/jinja2_transformer.py of the Jinja2 Handler component, results in improper neutralization of special elements used in a template engine. The attack can be launched remotely, and the exploit is publicly available.

An Open Redirect vulnerability in Dify AI Workflow's AppInitializer component. An attacker can redirect a user to a malicious site during OAuth flow, requiring user interaction (visiting a malicious page or file).

A SQL injection vulnerability in Dify before version 1.16.0-rc1 in the MyScale vector store backend allows attackers to execute arbitrary SQL by supplying unsanitized search parameters to the search_by_full_text method without escaping or parameterization. Attackers can inject malicious SQL through the search parameters to read, modify, or delete data in the underlying ClickHouse database.