DB-GPT: Hardcoded MySQL root credentials in default docker-compose.yml

Summary

DB-GPT through 0.8.2 ships a docker-compose.yml with a fixed MySQL root password (aa123456) and publishes MySQL port 3306 on all interfaces. An attacker who can reach port 3306, or any container on the shared dbgptnet network, can log in as root@% without further authentication and gain full access to all databases, including FILE and SUPER privileges. The issue applies to deployments that use the default compose file without changes.

Affected

• DB-GPT 0.8.2 and earlier (per CVE record: 0 to 0.8.2)
• Default docker-compose.yml from commit 83609c4 (v0.8.2 tag)
• Later copies of docker-compose.yml on main still show the same pattern, according to research notes

Fixed in

Unknown. No vendor advisory or patched release has been found for this CVE.

Workaround

• Remove the static MYSQL_ROOT_PASSWORD and use generated secrets or file-based Docker secrets
• Remove the MySQL ports mapping, or bind it to 127.0.0.1 only
• Keep the database on the internal Docker network only
• Do not run the webserver as MySQL root; create a least-privilege application user
• Rotate any password that was used with the default file

Exploitation

• CISA SSVC in the CVE record lists exploitation as poc and automatable as yes
• No public exploit confirmed by the research notes; VulDB states no exploit is available
• No evidence of exploitation in the wild found; KEV status not confirmed
• Exploitation requires only network access to port 3306 or the shared Docker network

Our recommendation

• Check whether any DB-GPT deployment runs the default docker-compose.yml and whether port 3306 is listening on a host or public interface
• Change the MySQL root password and remove the static value from all configuration
• Remove the host port publication for MySQL or restrict it with firewall rules
• Create a dedicated application database user without superuser rights
• Review database logs and data for unauthorised access if the default setup was exposed

Public exploits iAttack code is publicly available (PoC on GitHub, Metasploit or Exploit-DB).

PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.

Research sources

• CVE record reference: DB-GPT docker-compose.yml at commit 83609c4 github.com
• Lasso vulnerability database: CVE-2026-77933 www.lasso.security
• VulnCheck advisory: DB-GPT hardcoded MySQL root credentials www.vulncheck.com
• VulDB: CVE-2026-77933 vuldb.com
• VulDB: vulnerability 422593 vuldb.com
• DB-GPT docker-compose.yml on main github.com
• Docker Compose: using secrets docs.docker.com
• DB-GPT releases github.com

Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 01:12.