dbcve.org
DifyApplication · Langgenius

CVE-2025-56157

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 1.5.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Dify through version 1.5.1 ships with hardcoded PostgreSQL credentials in its docker-compose.yaml configuration file. Anyone with access to the source code can obtain these default database credentials, potentially allowing unauthorized access to the application's PostgreSQL database.

MitigationChange the default PostgreSQL username and password in docker-compose.yaml to strong, unique credentials before deployment. Ensure PostgreSQL port 5432 is not exposed to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DifyApplication
Affected:<= 1.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Dify is deployed
    Look for Dify installation directories, docker containers, or check running services that match Dify naming patterns (e.g., 'dify', 'docker-compose.yml' files with Dify configurations)
    Affected if Dify software is present in the environment
  2. Check installed Dify version
    Locate the docker-compose.yaml or docker-compose.yml file in the Dify deployment directory and inspect the image tags or version references. Alternatively, check container labels if Dify is already running: docker ps --format '{{.Names}} {{.Labels}}' | grep dify
    Affected if The installed version is 1.5.1 or any version <= 1.5.1
  3. Inspect docker-compose.yaml for hardcoded credentials
    Open the docker-compose.yaml file in the Dify deployment directory and search for PostgreSQL configuration sections (typically under 'services' > 'db' or similar). Look for 'POSTGRES_USER' and 'POSTGRES_PASSWORD' environment variables or similar fields
    Affected if Default or static username and password values are present in plain text within the configuration file
  4. Verify credential exposure risk
    Check if the source code repository or deployment files containing docker-compose.yaml are accessible to unauthorized users, or if the file has been committed to version control with default credentials
    Affected if The docker-compose.yaml file with hardcoded credentials is accessible to users who should not have database credentials

A user is affected if Dify version 1.5.1 or lower is deployed and the docker-compose.yaml configuration contains hardcoded PostgreSQL username and password values that could be obtained by unauthorized parties.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.5.1
Vendor patch github.com →
Interim mitigation

Change the default PostgreSQL username and password in docker-compose.yaml to strong, unique credentials before deployment. Ensure PostgreSQL port 5432 is not exposed to untrusted networks.

Recommended fix Moderate confidence
  1. 1. Identify current Dify version by checking the deployed docker-compose.yaml or application metadata
  2. 2. Review the changes in vendor patch/commit https://github.com/langgenius/dify/pull/15286 to understand the fix
  3. 3. Plan upgrade to a release version that incorporates the merged fix for CVE-2025-56157
  4. 4. Before upgrading, regenerate all database credentials (PostgreSQL password and any other hardcoded secrets)
  5. 5. Update docker-compose.yaml with new credentials before deploying the upgraded version
  6. 6. Verify no unauthorized access occurred and review access logs for PostgreSQL port 5432
  7. 7. After upgrade, ensure PostgreSQL is not exposed to untrusted networks
Caveat Ensure all service configurations using the old hardcoded credentials are updated with the new credentials before deploying the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dify Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-56157 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-56157 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data