Is CVE-2026-41947 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41947 being exploited in the wild.

How severe is CVE-2026-41947?

High severity, with a CVSS score of 7.4, published 18 May 2026.

Is there a fix for CVE-2026-41947?

A patch was published on 2026-05-14: Fix merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41947 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-41947?

Check whether you run Langgenius Dify at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41947: Dify authorization bypass in trace configuration endpoints

CVE-2026-41947 · Severity: high · CVSS 7.4 · Published 2026-05-18

Dify, an open-source platform for building AI applications, contains a security flaw in how it manages application tracing configurations. An attacker with a standard account can bypass security checks to modify the settings of applications belonging to other organizations. This allows the attacker to redirect sensitive AI chat logs and responses to their own servers, potentially exposing confidential business data and user interactions.

Technologies: Langgenius Dify. Vendors: Langgenius.

Quick answers

Is CVE-2026-41947 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41947 being exploited in the wild.
How severe is CVE-2026-41947?: High severity, with a CVSS score of 7.4, published 18 May 2026.
Which products and versions are affected?: Langgenius Dify <= 1.14.1.
Is there a fix for CVE-2026-41947?: A patch was published on 2026-05-14: Fix merged into main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41947 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-41947?: Check whether you run Langgenius Dify at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An authorization bypass vulnerability (CWE-639) exists in Dify's trace configuration endpoints (/console/api/apps/<app_id>/trace-config). The application fails to perform tenant ownership validation when processing GET, POST, PATCH, and DELETE requests for these endpoints. An authenticated attacker can provide a victim's app_id to read or modify tracing settings, enabling the redirection of LLM prompts and responses to attacker-controlled Langfuse or OpenTelemetry endpoints. While the CVSS vector suggests high complexity, the vulnerability is easily reachable due to Dify Cloud's free self-registration. The issue was addressed in pull request #35793 by enforcing tenant scoping via the @get_app_model decorator.

Affected products

langgenius Dify <= 1.14.1

Timeline

2026-05-05: other: Initial fix proposed in pull request
2026-05-14: patched: Fix merged into main branch
2026-05-18: disclosed: CVE published and NVD record created

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.