CVE-2026-41947
Auth bypass in Dify lets editors set traces for any tenant, redirecting data to attacker LLM providers.
Is CVE-2026-41947 being exploited?
Not confirmed. CVE-2026-41947 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 6.0% probability of exploitation in the next 30 days.
How severe is CVE-2026-41947?
CVE-2026-41947 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41947?
Yes. A fix has been recorded for CVE-2026-41947. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41947 affect?
CVE-2026-41947 affects Dify (versions <= 1.14.1), Dify Cloud (unauthenticated self-registration). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41947?
Limit editor rights; monitor trace config activity; patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated editors can set tenant-agnostic trace configs, redirecting data to attacker-controlled LLM providers; potential data exposure.
Monitor only
- affected< 1.14.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.