Key points
- DB-GPT through version 0.8.2 contains a critical hardcoded credentials vulnerability.
- The default docker-compose.yml sets a static MYSQL_ROOT_PASSWORD and publishes port 3306 on all interfaces.
- Attackers can authenticate as root@% to gain full database access including FILE and SUPER privileges.
DB-GPT versions up to and including 0.8.2 are affected by a critical security flaw identified as CVE-2026-77933. According to the National Vulnerability Database, this issue allows unauthorized users to access the underlying MySQL database with root-level privileges. The vulnerability stems from the default configuration files provided by eosphoros-ai, which hardcode sensitive authentication details. The source material does not state whether a fix or updated version exists.
In plain English
The default setup for DB-GPT includes a file named docker-compose.yml that configures how the application runs. This file contains a fixed password for the MySQL root user, meaning every installation uses the same secret key. Furthermore, the configuration publishes the database port, 3306, on all network interfaces. This means the database is visible to any device that can reach the server, rather than being restricted to the local machine or a private network segment.
The background
The flaw is classified under CWE-1392, which relates to hardcoded credentials. Because the password is static and included in the default deployment script, it is known to anyone who reviews the configuration or intercepts the setup process. The National Vulnerability Database rates the severity as 9.3, which is considered critical. This high score reflects the ease of exploitation and the severe impact of gaining root access to the database.
What changes now
Organizations using DB-GPT must immediately audit their deployments. Since the vulnerability exists in the default docker-compose.yml, any instance running version 0.8.2 or older is likely exposed. Attackers who can reach port 3306 or the shared dbgptnet network can authenticate as root@%. This grants them full database access, including powerful FILE and SUPER privileges that allow them to read, modify, or delete data and execute system commands.
Who needs to act first
Teams should prioritize systems exposed to the internet or untrusted networks.
What to do and how to stay safe
- Out-of-band patches address high-severity flaws that cannot wait for monthly or quarterly maintenance windows.
- The lack of rigorous testing increases the risk of breaking dependent applications or services.
- Automated deployment tools are necessary to manage the chaos of sudden, widespread updates.
Step-by-step guide: Out-of-Band Patches: Meaning, Risks, and Deployment Reality
General security guidance from the Patch Herald newsroom. It is not confirmed advice from the organisations named in this story.
