# CVE-2026-77933: DB-GPT through 0.8.2 Hardcoded MySQL Root Credentials in docker-compose Deployment


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-rq79-8cw2-45h7

## What is CVE-2026-77933?

CVE-2026-77933 is a critical vulnerability in eosphoros-ai DB-GPT, published on 20 Oct 2026. 

### Official description

DB-GPT through 0.8.2 contains a hardcoded credentials vulnerability in its default docker-compose.yml that sets a static MYSQL_ROOT_PASSWORD and publishes port 3306 on all interfaces. Attackers reaching port 3306 or the shared dbgptnet network can authenticate as root@% to gain full database access including FILE and SUPER privileges.

Weakness: CWE-1392 (Use of Default Credentials)

## Which versions are affected by CVE-2026-77933?


## How do I fix CVE-2026-77933?

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

## Is CVE-2026-77933 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77933 and fix it if it is affected.

What it is: CVE-2026-77933 is a critical vulnerability in eosphoros-ai DB-GPT, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77933 exists.

Affected product: eosphoros-ai DB-GPT. 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-2026-77933/ (Markdown: https://insights.sbomify.com/CVE-2026-77933/index.md)
```

## Sources

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

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