DB-GPT 0.8.2 Exposes MySQL Root Credentials via Default Docker Configuration

The National Vulnerability Database has assigned CVE-2026-77933 to a critical security flaw in eosphoros-ai DB-GPT. This vulnerability allows unauthorized users to gain full administrative access to the application's MySQL database. The issue stems from hardcoded credentials found in the default deployment configuration files for versions through 0.8.2.

According to the NVD record, the flaw carries a CVSS score of 9.3, which is classified as Critical. The weakness is categorized under CWE-1392, indicating an inclusion of sensitive information in a configuration file. Attackers who can reach the affected service on port 3306 or connect to the shared dbgptnet network can exploit this misconfiguration without needing to bypass authentication mechanisms.

Technical Details of the Exposure

The core issue lies within the default docker-compose.yml file provided with DB-GPT installations. This file sets a static MYSQL_ROOT_PASSWORD that remains unchanged unless manually edited by the administrator. Furthermore, the configuration publishes port 3306 on all network interfaces, making the database service accessible from any connected network segment rather than restricting it to localhost or internal containers.

An attacker gaining network access can authenticate as root@% using the hardcoded password. This grants them full database access, including high-privilege capabilities such as FILE and SUPER privileges. These permissions allow the attacker to read and write files on the host system and manage all database operations, potentially leading to complete compromise of the underlying infrastructure.

Scope of Affected Systems

The vulnerability affects eosphoros-ai DB-GPT through version 0.8.2. Any deployment using the default docker-compose.yml configuration without modifying the password or network binding settings is vulnerable. Organizations running these versions in production environments or development labs are at risk if the MySQL port is exposed to untrusted networks or the public internet.

The NVD record does not specify whether earlier versions before the current release cycle are affected, but it explicitly lists "through 0.8.2" as the affected range. Users of the dbgptnet shared network are also at risk, as the hardcoded credentials allow lateral movement within the container network if an attacker compromises any other service on that network segment.

What should you do?

Security teams should immediately audit their DB-GPT deployments for the presence of default docker-compose.yml configurations. Administrators must verify that the MYSQL_ROOT_PASSWORD has been changed from its static default value. Network rules should be reviewed to ensure that port 3306 is not published on all interfaces, restricting access to trusted internal networks only.