CVE-2026-41949

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreMEDIUM confidence

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

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-05-18. The CNA's CVSS baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Elevated
5.9EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (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: 5.9Exploit: No code on recordExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Dify before version 1.14.2 contains an authorization bypass vulnerability in the file preview endpoint that allows any authenticated user to read up to 3,000 characters of any uploaded document across all tenants and workspaces using only the file's UUID. Attackers can access the /console/api/files/{file_id}/preview endpoint with an intercepted file UUID to extract sensitive content from documents without ownership or workspace permission verification. NOTE: Dify Cloud allows unauthenticated free self-registration, making account creation trivially accessible to any attacker.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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)
Severity59% × 45%
The EG Score, 5.9 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 (3)

Auto-updated May 18, 2026
Fix referenced — no release confirmed yet.
Web page

Dify v1.14.1 Authorization Bypass via File Preview Endpoint | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dify-authorization-bypass-via-file-preview-endpoint
Web page

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

https://huntr.com/bounties/d50a0240-7951-4939-b989-9bded66c7682
Web page

fix(security): tenant-scope FilePreviewApi text-extract endpoint (GHSA-2qwc-c2cc-2xwv) by xr843 · Pull Request #35797 · langgenius/dify · GitHub

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

Vendor Advisories for CVE-2026-41949(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 / 25× 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 221 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 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41949?
CVE-2026-41949 is a medium-severity vulnerability; its CVE record was published on May 18, 2026. Dify before version 1.14.2 contains an authorization bypass vulnerability in the file preview endpoint that allows any authenticated user to read up to 3,000 characters of any uploaded document across all tenants and workspaces using only the file's UUID. Attackers can access the…
When was CVE-2026-41949 made public?
CVE-2026-41949 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-41949 actively exploited?
CVE-2026-41949 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41949?
CVE-2026-41949 has a CVSS base score of 5.9 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-41949?
A fix for CVE-2026-41949 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-41949 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-41949?

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

Book a Demo →Browse All CVEs