Skip to main content
EPSS 0.9%top 43%

CVE-2025-56157: n/a

0
Critical
VulnerabilityCVE-2025-56157cvecve-2025-56157
Published: 12/18/2025 (12/18/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

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.

CVSS v3.1

Score 9.8critical

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected software

GitHub Actionsmore threats →ai
langgenius/dify
pkg:github/langgenius/dify
Affected versions
<=1.5.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/05/2026, 21:27:31 UTC

Technical Analysis

CVE-2025-56157 describes a critical vulnerability in Dify up to version 1.5.1 where default PostgreSQL usernames and passwords are specified in the docker-compose.yaml file included in the source code. This constitutes a CWE-798 (Use of Hard-coded Credentials) weakness. The supplier notes that from version 1.0.1 onward, the Docker configuration does not expose PostgreSQL on TCP port 5432 by default, reducing exposure risk. However, if PostgreSQL is reachable, the default credentials allow unauthenticated attackers to fully compromise the database. The CVSS v3.1 base score is 9.8, reflecting network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability.

Potential Impact

If an attacker can access the PostgreSQL service, the default credentials allow full unauthorized access, leading to complete compromise of the database's confidentiality, integrity, and availability. This can result in data theft, data manipulation, or denial of service. The risk is mitigated if the PostgreSQL port is not exposed externally, as stated by the supplier for versions 1.0.1 and later.

Mitigation Recommendations

No official patch or fix is currently documented. Users should ensure that PostgreSQL is not exposed externally, as per the supplier's configuration starting from version 1.0.1. Additionally, users must change default credentials immediately if the database is accessible to prevent unauthorized access. Monitor vendor advisories for any forthcoming official fixes or updates.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-08-16T00:00:00.000Z
State
PUBLISHED

Threat ID: 69444aef4eb3efac36a086bd

Added to database: 12/18/2025, 18:41:51 UTC

Last enriched: 07/05/2026, 21:27:31 UTC

Last updated: 09/10/2026, 19:36:51 UTC

Views: 315

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses