CVE-2026-41947

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 6.0%, top 7% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 6%CVSS: 9.1Exploit: Elevated riskExposed: 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
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
6%
EPSS %ILE
93%
KEV
Not listed

Published

May 18, 2026

Last Modified

July 14, 2026

Advisory Details (6)

Auto-updated Aug 1, 2026
Patch available. Sources: github_pr, github_commit, github_release.
generic

Dify < 1.14.2 Authorization Bypass via Trace Configuration Endpoints | Advisories | VulnCheck

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

commit 55d05fe52de8 (langgenius/dify)

Fix landed in langgenius/dify commit 55d05fe52de8 — awaiting tagged release

https://github.com/langgenius/dify/commit/55d05fe52de880cd8497df8cea052351c594fad8
github_pr

fix(security): enforce tenant scoping on app trace-config endpoints (GHSA-48xc-wmw8-3jr3)

Fix merged in langgenius/dify PR #35793 on 2026-05-14 — awaiting tagged release

https://github.com/langgenius/dify/pull/35793
github_release Patch Available

v1.14.2 - Security fixes, agent groundwork, workflow reliability, and deployment updates

Patch available: langgenius/dify 1.14.2

https://github.com/langgenius/dify/releases/tag/1.14.2
generic

DifyTap: Zafran discovers how attackers can silently wiretap AI data across tenants on a platform powering 1M+ apps

https://www.zafran.io/resources/difytap-zafran-discovers-how-attackers-can-silently-wiretap-ai-data-across-tenants-on-a-platform-powering-1m-apps
generic

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

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

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 10× in last 7d / 102× 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 240 total refreshes for this CVE.

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

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 July 14, 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 6% probability of exploitation in the next 30 days, which ranks it in the top 7.2% of all scored CVEs.
What is the CVSS score of CVE-2026-41947?
CVE-2026-41947 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
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.

Start Free Scan →Browse All CVEs