CVE-2026-41947: Dify Authorization Bypass via Trace Configuration Endpoints (before 1.14.2)

Overview

CVE-2026-41947 is an authorization bypass classified as CWE-639 (authorization bypass through a user-controlled key, also called IDOR). According to the record, an authenticated editor can configure and enable tracing for applications that belong to other tenants, because the trace configuration endpoints do not verify tenant ownership.

Impact

• Confidentiality: the record states that messages and responses from affected applications could be redirected to attacker-controlled LLM trace providers, which would expose prompt and response data.
• Integrity: the CVSS vector in the record rates integrity impact as high.
• Severity: NVD and VulnCheck list a base score of 9.1 with a critical rating. GitHub lists a lower score of 7.4 for the same CVE.

Affected products and versions

• Dify versions before 1.14.2. The record lists the affected range as up to and including 1.14.1, under the product names Dify Dify and Langgenius Dify.
• The record references version 1.14.2 as the release containing the fix.
• Dify Cloud is mentioned in the record because it offers free self-registration without authentication, which lowers the barrier to obtaining an account.

Exploitation status

The record does not list this CVE in the CISA KEV catalog, so no confirmed active exploitation is recorded in the sources consulted. The record includes an SSVC exploitation value of proof of concept and some references are tagged as exploit-related, which indicates that technical material exists publicly. This analysis does not describe that material.

Remediation and mitigation

• Upgrade self-hosted Dify deployments to version 1.14.2 or the release that contains the fix referenced in the release notes.
• Confirm with the Dify Cloud provider whether the hosted service has received the fix, because the record does not state this.
• Until the upgrade is applied, review which users hold the editor role and remove unnecessary editor access.
• Where feasible, restrict or review open self-registration on affected instances.

Detection guidance

• Review audit or application logs for changes to trace or observability settings and confirm that each change was made by a user who owns the application.
• Alert on trace configurations that point to external provider endpoints not approved by your organization.
• Review recently created accounts, especially those that gained editor privileges shortly after creation.

Limitations of the available information

• The record says exploitation requires an authenticated editor, while the CVSS vector lists no privileges required. This inconsistency is not resolved in the sources consulted.
• The record does not name the exact endpoints or the exact code paths affected.
• It is unknown from the record whether a new editor account on Dify Cloud can obtain the editor role without administrator action.
• The EPSS entry is dated after the publication date in the record, so its timing should be interpreted with caution.

Frequently asked questions

What is CVE-2026-41947?

It is an authorization bypass in Dify's trace configuration endpoints. According to the record, authenticated editors can configure tracing for applications in other tenants.

Which versions are affected?

The record lists Dify before 1.14.2, with an affected range up to and including 1.14.1. The release referenced as fixed is 1.14.2.

Is this CVE being actively exploited?

The record does not list it in CISA KEV, and no confirmed exploitation in the wild appears in the sources consulted. Public technical material exists, so prompt patching is advisable.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.