Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
CriticalPublic exploit

Authorization bypass in Dify trace configuration endpoints

IdentifiersCVE-2026-41947CWE-639· Authorization Bypass Through…

CVE-2026-41947 affects Dify before version 1.14.2 (including 1.14.1 and prior). The vulnerability is an authorization bypass in Dify's tracing system caused by missing tenant ownership validation in the trace configuration endpoints. An authenticated user with editor-level access can set and enable trace configurations for applications outside their own tenant/workspace. By abusing these endpoints, an attacker can register an attacker-controlled LLM trace provider for a victim application and cause the application's traced traffic to be forwarded externally. Public reporting describes this as a tracing hijack that can be used against any application the attacker can access as a client, including publicly accessible applications in multi-tenant deployments.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows cross-tenant compromise of confidentiality and integrity for affected Dify applications. An attacker can redirect traced application data, including user messages, prompts, chat histories, and model responses, to attacker-controlled infrastructure, creating a persistent exfiltration channel. The flaw enables unauthorized modification of tracing settings on victim applications and can expose sensitive AI workflow data belonging to other customers in shared Dify environments. Available reporting does not indicate a direct availability impact.

Mitigation

If you can’t patch tonight, do this now.

Until patching is completed, restrict access to trace configuration endpoints to trusted administrative paths only, reduce or remove editor access where not strictly required, and closely monitor for changes to tracing providers and trace enablement state. In Dify Cloud or similar environments where account creation is easy, monitor for suspicious newly created accounts and anomalous cross-tenant activity. If possible, disable tracing or outbound connections to unapproved trace backends, and enforce tenant ownership validation through compensating controls such as API gateway or application-layer authorization checks.

Remediation

Patch, then assume compromise.

Upgrade Dify to version 1.14.2 or later, which addresses the missing tenant ownership checks in the trace configuration functionality. After upgrading, review and reset trace configurations for all applications, verify that no unauthorized external trace providers are configured, rotate any credentials or secrets that may have been exposed through traced traffic, and audit logs for suspicious changes to tracing settings or unexpected outbound trace destinations.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
DifyDifyapplication
LanggeniusDifyapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.