CVE-2026-41947

CRITICALNVD 9.17.4
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-18. NVD baseline CVSS 9.1; sources differ by 1.7.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
7.4(medium)
EPSS
36.4%
KEV
Not listed

Published

May 18, 2026

Last Modified

June 22, 2026

Advisory Details (3)

Auto-updated May 18, 2026
No patch confirmed yet.
generic

Dify v1.14.1 Authorization Bypass via Trace Configuration Endpoints | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dify-authorization-bypass-via-trace-configuration-endpoints
generic

huntr - The world’s first bug bounty platform for AI/ML

https://huntr.com/bounties/a43076b2-fbc8-4750-9647-89a036b52f52
generic

fix(security): enforce tenant scoping on app trace-config endpoints (GHSA-48xc-wmw8-3jr3) by xr843 · Pull Request #35793 · langgenius/dify · GitHub

https://github.com/langgenius/dify/pull/35793

Vendor Advisories for CVE-2026-41947(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 65× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 159 total refreshes for this CVE.

  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:15 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-29 21:10 UTCEG score recompute
  15. 2026-06-29 21:10 UTCGHSA enrichment
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 08:40 UTCEG score recompute
  19. 2026-06-28 08:40 UTCGHSA enrichment
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 21:23 UTCEG score recompute
  22. 2026-06-27 21:23 UTCGHSA enrichment
  23. 2026-06-27 07:44 UTCEG score recompute
  24. 2026-06-27 07:44 UTCGHSA enrichment
  25. 2026-06-27 03:08 UTCEPSS rescore
Show 75 more
  1. 2026-06-26 19:57 UTCEG score recompute
  2. 2026-06-26 19:57 UTCGHSA enrichment
  3. 2026-06-26 04:54 UTCEG score recompute
  4. 2026-06-26 04:54 UTCGHSA enrichment
  5. 2026-06-25 17:47 UTCEG score recompute
  6. 2026-06-25 17:47 UTCGHSA enrichment
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 13:49 UTCEPSS rescore
  9. 2026-06-24 14:05 UTCEPSS rescore
  10. 2026-06-23 21:33 UTCEPSS rescore
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-22 14:25 UTCEPSS rescore
  13. 2026-06-21 14:56 UTCEPSS rescore
  14. 2026-06-21 14:56 UTCEPSS rescore
  15. 2026-06-21 01:59 UTCEPSS rescore
  16. 2026-06-19 19:25 UTCEPSS rescore
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-18 02:24 UTCEG score recompute
  20. 2026-06-18 02:23 UTCGHSA enrichment
  21. 2026-06-17 17:53 UTCEPSS rescore
  22. 2026-06-17 13:16 UTCEG score recompute
  23. 2026-06-17 13:15 UTCGHSA enrichment
  24. 2026-06-16 22:08 UTCEG score recompute
  25. 2026-06-16 22:08 UTCGHSA enrichment
  26. 2026-06-16 17:52 UTCEPSS rescore
  27. 2026-06-16 10:55 UTCEG score recompute
  28. 2026-06-16 10:55 UTCGHSA enrichment
  29. 2026-06-15 23:12 UTCEG score recompute
  30. 2026-06-15 23:12 UTCGHSA enrichment
  31. 2026-06-15 17:49 UTCEPSS rescore
  32. 2026-06-15 00:13 UTCEG score recompute
  33. 2026-06-15 00:13 UTCGHSA enrichment
  34. 2026-06-14 13:07 UTCEG score recompute
  35. 2026-06-14 13:07 UTCGHSA enrichment
  36. 2026-06-14 02:00 UTCEG score recompute
  37. 2026-06-14 02:00 UTCGHSA enrichment
  38. 2026-06-13 23:00 UTCEPSS rescore
  39. 2026-06-13 14:54 UTCEG score recompute
  40. 2026-06-13 14:54 UTCGHSA enrichment
  41. 2026-06-12 23:42 UTCEG score recompute
  42. 2026-06-12 23:42 UTCGHSA enrichment
  43. 2026-06-12 23:12 UTCEPSS rescore
  44. 2026-06-12 23:12 UTCEPSS rescore
  45. 2026-06-12 12:32 UTCEG score recompute
  46. 2026-06-12 12:32 UTCGHSA enrichment
  47. 2026-06-12 01:26 UTCEG score recompute
  48. 2026-06-12 01:26 UTCGHSA enrichment
  49. 2026-06-11 14:19 UTCEG score recompute
  50. 2026-06-11 14:19 UTCGHSA enrichment
  51. 2026-06-11 14:00 UTCEPSS rescore
  52. 2026-06-11 03:12 UTCEG score recompute
  53. 2026-06-11 03:12 UTCGHSA enrichment
  54. 2026-06-10 22:18 UTCEPSS rescore
  55. 2026-06-10 16:05 UTCEG score recompute
  56. 2026-06-10 16:05 UTCGHSA enrichment
  57. 2026-06-10 13:22 UTCEPSS rescore
  58. 2026-06-10 13:22 UTCEPSS rescore
  59. 2026-06-10 04:59 UTCEG score recompute
  60. 2026-06-10 04:59 UTCGHSA enrichment
  61. 2026-06-09 17:52 UTCEG score recompute
  62. 2026-06-09 17:52 UTCGHSA enrichment
  63. 2026-06-09 06:46 UTCEG score recompute
  64. 2026-06-09 06:46 UTCGHSA enrichment
  65. 2026-06-08 19:38 UTCEG score recompute
  66. 2026-06-08 19:38 UTCGHSA enrichment
  67. 2026-06-08 14:17 UTCEPSS rescore
  68. 2026-06-08 14:17 UTCEPSS rescore
  69. 2026-06-08 03:58 UTCEG score recompute
  70. 2026-06-08 03:58 UTCGHSA enrichment
  71. 2026-06-07 16:52 UTCEG score recompute
  72. 2026-06-07 16:52 UTCGHSA enrichment
  73. 2026-06-07 15:25 UTCEPSS rescore
  74. 2026-06-07 15:25 UTCEPSS rescore
  75. 2026-06-07 05:45 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-41947?
CVE-2026-41947 is a critical vulnerability published on May 18, 2026. 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…
When was CVE-2026-41947 disclosed?
CVE-2026-41947 was first published in the National Vulnerability Database on May 18, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41947 actively exploited?
CVE-2026-41947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41947?
CVE-2026-41947 has a CVSS v3 base score of 9.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.4.
How do I remediate CVE-2026-41947?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41947, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-41947

Explore →

Is Your Infrastructure Affected by CVE-2026-41947?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.