Dify up to 1.5.1 docker-compose.yaml default credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Dify up to 1.5.1. Impacted is an unknown function of the file docker-compose.yaml. This manipulation causes default credentials. This vulnerability is handled as CVE-2025-56157. There is not any exploit available.
Details
A vulnerability has been found in Dify up to 1.5.1 and classified as problematic. Affected by this vulnerability is some unknown processing of the file docker-compose.yaml. The manipulation with an unknown input leads to a default credentials vulnerability. The CWE definition for the vulnerability is CWE-1392. The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality. As an impact it is known to affect confidentiality. The summary by CVE is:
Default credentials in Dify thru 1.5.1. PostgreSQL username and password specified in the docker-compose.yaml file included in its source code. NOTE: the Supplier reports that the Docker configuration does not make PostgreSQL (on TCP port 5432) exposed by default in version 1.0.1 or later.
This vulnerability is known as CVE-2025-56157 since 08/16/2025. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Default credentialsCWE: CWE-1392
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/16/2025 CVE reserved12/18/2025 Advisory disclosed
12/18/2025 VulDB entry created
01/29/2026 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2025-56157 (🔒)
GCVE (CVE): GCVE-0-2025-56157
GCVE (VulDB): GCVE-100-337441
Entry
Created: 12/18/2025 22:14Updated: 01/29/2026 00:38
Changes: 12/18/2025 22:14 (50), 01/29/2026 00:38 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.