# CVE-2025-56157: Hardcoded credentials in n/a

> Hardcoded PostgreSQL credentials in Dify's Docker configuration allow attackers to access the database if the port is exposed.
 

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-f5cx-j2cw-pgfg

## What is CVE-2025-56157?

CVE-2025-56157 is a critical vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2025-56157?

It affects 1 product.


Products: Langgenius Dify.

## How do I fix CVE-2025-56157?

No fix has been published for CVE-2025-56157 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-56157 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56157 exists.

## Other vulnerabilities in n/a

- [CVE-2025-3466](https://insights.sbomify.com/CVE-2025-3466/): Unsanitized Input in langgenius/dify (critical 9.8)
- [CVE-2025-63386](https://insights.sbomify.com/CVE-2025-63386/): Misconfiguration in n/a (critical 9.1)
- [CVE-2025-63388](https://insights.sbomify.com/CVE-2025-63388/): Misconfiguration in n/a (critical 9.1)
- [CVE-2024-10252](https://insights.sbomify.com/CVE-2024-10252/): Code Injection in langgenius/dify (high 8.8)
- [CVE-2024-12776](https://insights.sbomify.com/CVE-2024-12776/): Authentication Bypass in langgenius/dify (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-56157 and fix it if it is affected.

What it is: CVE-2025-56157 is a critical vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56157 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-56157/ (Markdown: https://insights.sbomify.com/CVE-2025-56157/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-56157
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-56157
- OSV: https://osv.dev/vulnerability/CVE-2025-56157

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-56157/
Summaries are generated and may contain mistakes; the official description above is the record.