CVE-2026-41947

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.4 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-05-18) is not newer than that change (2026-07-14), so it does not.

Triggered by: Headline CVSS from the CNA's CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

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 (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 18, 2026

Last Modified

July 14, 2026

Advisory Details (6)

Auto-updated Sep 16, 2026
Patch available. Sources: github_release, github_pr, github_commit.
Web page

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 pull request

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
Web page

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

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

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

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 11× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 280 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 180 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41947?
CVE-2026-41947 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2026-41947 was made public on March 30, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on May 18, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-41947 actively exploited?
CVE-2026-41947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41947?
CVE-2026-41947 has a CVSS base score of 9.1 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-41947?
A fix for CVE-2026-41947 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-41947 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs