GCD AI RADAR

Dify

Filed as: dify

Records
37
Disclosed CVEs
37
Exploited (sev 3–4)
0
CISA KEV flagged
0

Newest record 2026-10-06 · 37 distinct CVE ids · open in the explorer (the explorer matches the first product a record names, so it can list fewer)

Patch now: confirmed exploitation or KEV · 0

Records at severity 3–4 (exploitation confirmed by CISA, the vendor or reporting) and records flagged as listed in CISA KEV. The KEV flag is the classifier’s cisa-kev tag or a source on the KEV catalog; it is recorded when the collector sees the listing, so a missing flag does not mean a CVE is absent from the catalog.

No record for Dify has confirmed exploitation or a KEV flag.

Disclosures by month · last 24 months

Nov ’2437 disclosed · peak 6 in Apr ’25Oct ’26

Disclosed CVEs, no confirmed exploitation · 37

  1. 2026-10-06
  2. 2026-10-05
  3. 2026-09-03
  4. 2026-09-03
  5. 2026-08-03
  6. 2026-07-29
  7. 2026-07-10
  8. 2026-05-18
  9. 2026-05-18
  10. 2026-05-18
  11. 2026-05-05
  12. 2026-05-04
  13. 2026-04-20
    CVE-2026-34082
    CVE-2026-34082: Authorization flaw in Dify allows chat deletion
    2 Disclosedbroken_access_control · infra_vuln
  14. 2026-04-20
  15. 2026-04-20
  16. 2026-04-20
  17. 2026-03-03
  18. 2026-02-27
  19. 2026-02-11
  20. 2026-01-05
    CVE-2025-67732
    CVE-2025-67732: API Key Exposure Vulnerability in Dify
    2 Disclosedinfra_vuln · api-key-exposure
  21. 2025-12-18
  22. 2025-12-18
  23. 2025-12-18
  24. 2025-12-18
  25. 2025-10-17
  26. 2025-09-30
  27. 2025-09-25
  28. 2025-07-07
  29. 2025-06-17
  30. 2025-04-28
  31. 2025-04-25
  32. 2025-04-18
  33. 2025-04-18
  34. 2025-04-18
  35. 2025-04-14
  36. 2025-03-20
  37. 2025-03-20

This page lists what has been reported, not what to do about it. Versions and fixes are in each linked advisory; check the vendor’s own advisory before acting.