CVE-2026-41947 Dify < 1.14.2 Authorization Bypass via Trace Configuration Endpoints

Critical 9.3 Published Updated

Authenticated editors can bypass tenant ownership checks to redirect application traffic to attacker-controlled trace providers, exposing sensitive data.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-41947?

CVE-2026-41947 is a critical missing authorization vulnerability in langgenius dify, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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. Attackers can exploit missing tenant ownership checks in the trace configuration endpoints to redirect all messages and responses from victim applications to attacker-controlled LLM trace providers. NOTE: Dify Cloud allows unauthenticated free self-registration, making account creation trivially accessible to any attacker.

Weakness: CWE-639

Which versions are affected by CVE-2026-41947?

It affects 1 product.

Products include Dify Dify.

How do I fix CVE-2026-41947?

No fix has been published for CVE-2026-41947 yet. Limit exposure of the affected software until one is available.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-41947 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41947 exists.

Sources

Also known as GHSA-48v9-p8g8-55vg.

Is CVE-2026-41947 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free