CVE-2025-63387VulnerabilityPublished 18 Dec 2025Updated 22 Jan 2026

CVE-2025-63387: dify · n/a

Affects difySource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · 29% EPSS · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 29.9% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Dec 2025
Detectable: evidence found.
nuclei template: Dify v1.9.1 - Broken Access Control
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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHublanggenius/dify`pkg:github/langgenius/dify`Other threats	Affected =1.9.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately audit their use of Dify software to identify instances of version 1.9.1 or earlier. Network-level controls should be implemented to restrict access to the /console/api/system-features endpoint, ideally limiting it to trusted internal IP addresses or VPN users only. Application-level mitigation requires applying proper authorization checks to ensure only authenticated and authorized users can access sensitive API endpoints. If patches become available, organizations must prioritize timely deployment. In the absence of patches, consider deploying Web Application Firewalls (WAFs) with custom rules to block unauthenticated requests to the vulnerable endpoint. Continuous monitoring and logging of access to this endpoint should be enabled to detect and respond to suspicious activity promptly. Security teams should also conduct penetration testing to verify the effectiveness of mitigations. Finally, raising user awareness and updating incident response plans to include this vulnerability will enhance preparedness.

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.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of system configuration data managed via Dify v1.9.1. Exposure of such data could lead to unauthorized disclosure of internal system details, potentially aiding attackers in crafting targeted attacks or lateral movement within networks. Sectors such as finance, healthcare, critical infrastructure, and government agencies that rely on Dify for system management could face increased risk of data breaches or espionage. The vulnerability does not directly impact system integrity or availability, but the confidentiality breach alone can have severe regulatory and reputational consequences under GDPR and other data protection laws. Additionally, the ease of exploitation without authentication means attackers can probe vulnerable systems remotely, increasing the attack surface. Organizations with internet-facing instances of Dify are particularly vulnerable. The absence of known exploits in the wild suggests a window of opportunity for proactive mitigation before active exploitation occurs.

Summary

CVE-2025-63387 identifies an insecure permissions vulnerability in Dify version 1.9.1. The vulnerability resides in the /console/api/system-features HTTP GET endpoint, which lacks proper authorization controls. This allows unauthenticated attackers to send requests directly to this endpoint and retrieve sensitive system configuration data without needing any credentials or session tokens. The vulnerability is categorized under CWE-284 (Improper Access Control). The CVSS v3.1 base score is 7.5, reflecting a high severity due to the vulnerability's network accessibility (AV:N), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction needed (UI:N). The impact affects confidentiality (C:H) but does not affect integrity (I:N) or availability (A:N). Although no patches or known exploits are currently reported, the exposure of sensitive configuration data could facilitate further attacks or reconnaissance by adversaries. The vulnerability was reserved in late October 2025 and published in mid-December 2025, indicating recent discovery and disclosure. The lack of authentication and authorization checks on a sensitive API endpoint represents a critical security oversight in Dify's access control mechanisms.

CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Jan 2026, 19:14 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-284

Technical details

References

Community reviews

Related threats