How severe is CVE-2026-41947?

CVE-2026-41947 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-41947 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (93rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-41947?

CVE-2026-41947 affects Dify. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-41947?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-41947 have an EU (EUVD) identifier?

Yes. CVE-2026-41947 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-30772.

When was CVE-2026-41947 published?

CVE-2026-41947 was published on 2026-05-18 and last updated on 2026-06-22.

CVE-2026-41947

CVE-2026-41947 is a critical-severity vulnerability in Dify with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-639.

Key facts

Severity: Critical (CVSS 3.x base score 9.1)
CVSS v4: 9.3
EPSS exploit prediction: 6% (93rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-30772
Weakness: CWE-639
Affected product: Dify
Published: 2026-05-18
Last modified: 2026-06-22

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.

Frequently asked questions

What is CVE-2026-41947?: 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.
How severe is CVE-2026-41947?: CVE-2026-41947 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-41947 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (93rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-41947?: CVE-2026-41947 affects Dify. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-41947?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-41947 have an EU (EUVD) identifier?: Yes. CVE-2026-41947 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-30772.
When was CVE-2026-41947 published?: CVE-2026-41947 was published on 2026-05-18 and last updated on 2026-06-22.

References

Affected products (1)

cpe:2.3:a:dify:dify:*:*:*:*:*:*:*:*

More vulnerabilities in Dify

CVE-2026-41948 — Critical (CVSS 9.4): Dify version 1.14.1 and prior contain a path traversal vulnerability that allows authenticated users to manipulate…
CVE-2026-61461 — High (CVSS 8.8): Dify before 1.16.0-rc1 contains a SQL injection vulnerability in the MyScale vector store backend that allows attackers…
CVE-2025-0185 — High (CVSS 8.8): A vulnerability in the Dify Tools' Vanna module of the langgenius/dify repository allows for a Pandas Query Injection…
CVE-2024-11822 — High (CVSS 7.5): langgenius/dify version 0.9.1 contains a Server-Side Request Forgery (SSRF) vulnerability. The vulnerability exists due…
CVE-2025-67732 — Medium (CVSS 6.5): Dify is an open-source LLM app development platform. Prior to version 1.11.0, the API key is exposed in plaintext to…
CVE-2026-26023 — Medium (CVSS 6.1): Dify is an open-source LLM app development platform. Prior to 1.13.0, a cross site scripting vulnerability has been…

All CVEs affecting Dify →

Other CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities

CVE-2025-40805 — Critical (CVSS 10.0): Affected devices do not properly enforce user authentication on specific API endpoints. This could facilitate an…
CVE-2024-45032 — Critical (CVSS 10.0): A vulnerability has been identified in Industrial Edge Management Pro (All versions < V1.9.5), Industrial Edge…
CVE-2026-62283 — Critical (CVSS 9.9): Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. Nezha versions 1.14.13…
CVE-2026-73656 — Critical (CVSS 9.9): Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. Prior to 4.5.6, POST…
CVE-2026-48765 — Critical (CVSS 9.9): TypeBot is a chatbot builder tool. Versions prior to 3.17.0 allow a low-privilege read collaborator to extract a…
CVE-2026-67622 — Critical (CVSS 9.9): Flowise through 3.1.4 contains an insecure direct object reference vulnerability in the OpenAI Assistants integration…

Browse all CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities →