CVE-2026-41947

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 6.0% (93rd 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-11-08), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-30772 (ENISA EUVD) · GHSA-48v9-p8g8-55vg (GitHub Security Advisories)Source: ENISA EUVD

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: 6.0%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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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
6.0%
EPSS %ILE
93rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
6.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

November 8, 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 15× in last 7d / 63× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 383 rows 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 283 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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 November 8, 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 6.0% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41947?
CVE-2026-41947 has a CVSS v3 base score of 9.1 (NVD).
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