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

Published May 18, 2026
·
Updated

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.

Affected Software

2 affected components
Dify dify<=1.14.1
Dify dify<=1.14.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Dify to a version that resolves this vulnerability.

    Fixed in 1.14.2
  2. Compensating control

    Restrict access to trace configuration endpoints so that authenticated editor users can only modify trace configurations for applications they own within their tenant.

  3. Compensating control

    For Dify Cloud, limit or disable unauthenticated free self-registration so attackers cannot trivially create accounts to exploit the trace configuration authorization bypass.

Event History

May 18, 2026
CVE Published
via MITRE·01:48 PM
Data Sourced
via MITRE·01:48 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 22, 2026
News Published
via Dark Reading·09:14 PM
Jun 23, 2026
News Published
via Dark Reading·12:27 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-41947?

CVE-2026-41947 is considered a critical vulnerability due to its potential to allow unauthorized access to sensitive application configurations.

2

How do I fix CVE-2026-41947?

To fix CVE-2026-41947, upgrade Dify to version 1.14.2 or later, which addresses the authorization bypass vulnerability.

3

Who is affected by CVE-2026-41947?

CVE-2026-41947 affects users of Dify version 1.14.1 and earlier, specifically those using the trace configuration features.

4

What type of vulnerability is CVE-2026-41947?

CVE-2026-41947 is classified as an authorization bypass vulnerability, allowing inappropriate access to configure trace settings.

5

Can unauthorized users exploit CVE-2026-41947?

Yes, CVE-2026-41947 can be exploited by authenticated editor users to bypass authorization checks for trace configurations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203