CVE-2025-67732: langgenius dify · Information Exposure
Affects langgenius difySource CVE Database V5
Not known to be exploited · CVSS 8.4 High : upgrade to 1.11.0 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.11.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 5 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade dify and langgenius/dify to 1.11.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| langgeniusdify | Affected
| Fixed in
|
GitHublanggenius/difypkg:github/langgenius/difyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade all instances of Dify to version 1.11.0 or later immediately to eliminate the API key exposure. 2. Audit and rotate any API keys that may have been exposed prior to patching to prevent unauthorized reuse. 3. Implement strict role-based access controls (RBAC) to limit non-administrator user privileges and reduce the risk of credential exposure. 4. Employ network segmentation and monitoring to detect unusual API usage patterns indicative of abuse. 5. Use environment variables or secure vaults to store API keys server-side, ensuring they are never exposed in frontend code or client-side logs. 6. Conduct regular security reviews and penetration testing focused on credential management and frontend/backend separation. 7. Educate developers and administrators on secure API key handling and the risks of exposing sensitive information in client-side code. 8. Monitor third-party service usage quotas closely to detect anomalies that may indicate unauthorized consumption.
Description
CVE-2025-67732 is a high-severity vulnerability in langgenius' open-source LLM app development platform, Dify, affecting versions prior to 1.11.0. The issue involves exposure of the API key in plaintext on the frontend, allowing non-administrator users to access and reuse it without authorization. This can lead to unauthorized access to third-party services, potentially exhausting service quotas or causing service disruptions. The vulnerability requires no user interaction and can be exploited remotely with low complexity. The flaw impacts confidentiality by exposing sensitive credentials and could indirectly affect availability by depleting service quotas. The vendor fixed the issue in version 1.11.0 by removing API key exposure.