Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalPublic exploit

Dify trace configuration authorization bypass

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

CVE-2026-41947 is an authorization bypass vulnerability in Dify before version 1.14.2 affecting the tracing functionality used for profiling, monitoring, and logging application messages and model responses. The vulnerable trace configuration endpoints fail to validate tenant ownership, allowing an authenticated editor user to set and enable trace configurations for arbitrary applications regardless of which tenant owns them. By abusing these missing tenant ownership checks, an attacker can register an attacker-controlled LLM trace provider for a victim application and cause the victim application's prompts, messages, responses, and chat history to be forwarded externally. Public reporting describes this as a tracing hijack that can be used against publicly accessible applications on the same Dify instance.

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 enables cross-tenant confidentiality and integrity compromise. An attacker can redirect tracing for victim applications to infrastructure they control, creating a persistent exfiltration channel for application messages, prompts, model responses, and chat histories. This can expose sensitive customer conversations and AI workflow data from other tenants. Integrity is also affected because the attacker can alter trace configuration state for applications they do not own. No direct availability impact is described in the provided material.

Mitigation

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

Until fully remediated, restrict access to trace configuration endpoints to trusted administrative paths only, enforce tenant ownership checks at any reverse proxy or API gateway layer where possible, and monitor for creation or modification of trace providers and trace enablement events. In Dify Cloud or similar environments with low-friction account creation, audit newly created accounts and review publicly accessible applications for unauthorized tracing changes. Logging and alerting on trace configuration updates can help detect exploitation.

Remediation

Patch, then assume compromise.

Upgrade Dify to version 1.14.2 or later. The fix is described as adding the missing tenant ownership validation in the trace configuration endpoints. After upgrading, review all existing trace configurations and enabled trace providers for unauthorized changes, especially in multi-tenant and cloud deployments, and rotate or revoke any attacker-controlled tracing destinations if compromise is suspected.
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 activity6

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