CVE-2025-67732: high-severity vulnerability in langgenius dify
Dify Vulnerable to Plaintext API Key Exposure via Model Provider Configuration Endpoint
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.4epss 0.4%
Dify is an open-source LLM app development platform. Prior to version 1.11.0, the API key is exposed in plaintext to the frontend, allowing non-administrator users to view and reuse it. This can lead to unauthorized access to third-party services, potentially consuming limited quotas. Version 1.11.0 fixes the issue.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:L
Affected products
langgenius · difyRelated CVEs — langgenius dify
In the same product, most dangerous first.
CVE-2026-41948CRITICALDify v1.14.1 Path Traversal via Plugin Daemon Internal API AccessEPSS 22.7%CVE-2025-58747LOWDify MCP OAuth Flow Vulnerable to XSSEPSS 6.0%CVE-2026-41947CRITICALDify < 1.14.2 Authorization Bypass via Trace Configuration EndpointsEPSS 6.0%CVE-2026-28288MEDIUMDify has a user enumeration issueEPSS 0.7%CVE-2026-85021MEDIUMlanggenius dify Splash Layout splash.tsx router.replace cross site scriptingEPSS 0.5%CVE-2026-61461HIGHDify < 1.16.0-rc1 SQL Injection via MyScale Vector Store search_by_full_textEPSS 0.5%