CVE-2025-63387Dify Vulnerability
Dify v1.9.1 is vulnerable to Insecure Permissions.
Published Dec 18, 2025 · Updated Oct 20, 2026 · Also known as PYSEC-2025-103
Key Facts
Patch immediately- CVE-2025-63387 is a high-severity vulnerability (CVSS 7.5 v3.1) affecting Dify (Langgenius), dify-client (pypi).
- It is exploited in the wild, listed in Industry KEV feed since Jan 14, 2026. No public exploit code is known.
- EPSS estimates a 30% probability of exploitation in the next 30 days.
- No fixed version is listed yet; check the vendor advisory for mitigations.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Scores
CVSS v3.1
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (30-day exploit likelihood)
30%
Higher than 98.2% of all scored CVEs
Exploit maturity
Exploited (KEV)
ATLAS score
53/100
Publication score, see How it works
Exploitation Verdict
KEV listed
Jan 14, 2026
27 days after publication
Federal due date
None
No federal due date
Ransomware use
Not reported
Attributed actors
None named
Exploit & Defence Guidance
Exploit maturity
Exploited (KEV)
Public exploit code
0
Proof-of-concept links
In-the-wild evidence
1
Reports of active use
Advisories And Exploit References
- advisoryhttps://www.cve.org/CVERecord?id=CVE-2025-63387
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2025-63387
- advisoryhttps://gist.github.com/Cristliu/cddc0cbbf354de51106ab63a11be94af
- advisoryhttps://github.com/langgenius/dify/discussions
- advisoryhttps://github.com/langgenius/dify/issues/31368#issuecomment-3783712203
- patchhttps://github.com/langgenius/dify/pull/31392
Description
Dify v1.9.1 is vulnerable to Insecure Permissions. An unauthenticated attacker can directly send HTTP GET requests to the /console/api/system-features endpoint without any authentication credentials or session tokens. The endpoint fails to implement proper authorization checks, allowing anonymous access to sensitive system configuration data.
NOTE: The maintainer states that the endpoint is unauthenticated by design and serves as a bootstrap mechanism required for the dashboard initialization. They also state that the description inaccurately classifies the returned data as sensitive system configuration, stating that the data is non-sensitive and required for client-side rendering. No PII, credentials, or secrets are exposed.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| Industry KEV feed | Jan 14, 2026 | n/a | Not reported |
Affected Products
2 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| DifyLanggenius | 1.9.1 | n/a |
| dify-clientpypi | See advisory | n/a |
Timeline
Publicly disclosed
Dec 18, 2025
Added to Industry KEV feed
Jan 14, 2026
Last updated
Oct 20, 2026
Weakness Type
- CWE-284 Improper Access Control
References
- advisorycve.org · CVERecord
- advisorynvd.nist.gov · CVE-2025-63387
- advisorygist.github.com · cddc0cb
- advisorygithub.com · discussions
- advisorygithub.com · 31368
FAQ
Common Questions.
Dify v1.9.1 is vulnerable to Insecure Permissions.
Affected: Dify (Langgenius) versions 1.9.1; dify-client (pypi). The full list is in the CVE brief.
It is exploited in the wild, listed in Industry KEV feed since Jan 14, 2026.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
No fixed version is listed yet; check the vendor advisory for mitigations.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2025-63387 On Your Attack Surface?
Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.
Request A Demo