External risk intelligence

DB-GPT Hardcoded MySQL Root Credentials Allow Full Database Access

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-77933

The vulnerability involves a default configuration that explicitly exposes the database port 3306 on all interfaces via a provided docker-compose.yml file. Because this configuration makes the database reachable across the network by default upon deployment, it creates a commonly reachable service in many standard containerized deployment environments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in DB-GPT, a technology that interacts with databases. The issue stems from hardcoded credentials within its default configuration, which could allow unauthorized access to sensitive database information if not properly secured.

Default configuration allows unauthorized database access.
Leaders should remember this for potential data exposure.
Confirm if this technology is deployed within our environment.

Attack Path

How an attacker could exploit the issue

An attacker could gain unauthorized access to the database by connecting to the exposed MySQL port or the internal Docker network. This is possible because the default configuration includes hardcoded root credentials for the MySQL database. Once authenticated, the attacker could perform any database operation, including reading and modifying data, and potentially executing system commands.

Unauthenticated network access to port 3306.
Connecting to the exposed MySQL port.
Full database control and potential system access.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow unauthorized users to gain full control of the database. Attackers could exploit this by reaching the database port on all network interfaces or by accessing the shared Docker network. The hardcoded credentials in the default Docker configuration enable root-level database access, including the ability to execute arbitrary commands and access all data.

Full database access, including sensitive data.
Unauthenticated network access to the database.
Data loss or unauthorized data modification.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in DB-GPT's default Docker configuration exposes a hardcoded root password for its MySQL database, making it accessible to attackers on any network interface. The immediate priority is to identify all deployments of DB-GPT using the default `docker-compose.yml`, determine their exposure to the network, and confirm their business criticality. Once identified, the accountable owner must be engaged to plan remediation, potentially involving immediate credential changes, network isolation, or a full system update.

Identify DB-GPT deployments and assess exposure.
Confirm business criticality and accountable owner.
Plan remediation based on risk and vendor coordination.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is DB-GPT and how is it used?

DB-GPT is an open-source framework designed to help developers build applications that interact with databases using Large Language Models. It acts as an interface layer, allowing users to query and manage data through natural language processing. By integrating database connectivity into AI workflows, it simplifies how technical teams extract insights or automate tasks across their data infrastructure.

What does the CVE-2026-77933 vulnerability mean?

This vulnerability is classified as Use of Hardcoded Credentials (CWE-1392). In this case, the software's default deployment file includes a static, pre-set password for the MySQL root account. Because this password is publicly known and embedded in the configuration, an attacker can use it to log into the database as an administrator without needing to guess or crack a unique secure password.

How can an attacker trigger this security flaw?

The flaw is triggered when the default docker-compose.yml configuration is used to deploy the service. This setup publishes port 3306 on all network interfaces. An attacker who can reach this port over the network, or who has access to the shared Docker network used by the container, can use the hardcoded credentials to gain unauthorized entry. Simply using default settings in this specific version creates the precondition for access.

Is my environment at risk for CVE-2026-77933?

According to Halo Surface Signal, this vulnerability is considered highly relevant because the default deployment configuration explicitly publishes the database port to all available network interfaces. If you are running DB-GPT versions through 0.8.2 using the provided default configuration, your database is likely reachable across your network, increasing the probability of unauthorized discovery and access.

How do I secure a system running DB-GPT?

First, identify all instances of DB-GPT in your infrastructure that were deployed using the default configuration. Immediately restrict network access to port 3306 so it is not exposed to the public internet or untrusted internal segments. Change the hardcoded MySQL root password to a unique, strong credential, and ensure that any shared Docker networks are properly isolated according to your security policies.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.