eosphoros-ai DB-GPT up to 0.8.2 docker-compose.yml hard-coded credentials

Summaryinfo

A vulnerability has been found in eosphoros-ai DB-GPT up to 0.8.2 and classified as critical. The affected element is an unknown function of the file docker-compose.yml. This manipulation causes hard-coded credentials. This vulnerability appears as CVE-2026-77933. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in eosphoros-ai DB-GPT up to 0.8.2. It has been declared as critical. Affected by this vulnerability is an unknown part of the file docker-compose.yml. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at lasso.security. This vulnerability is known as CVE-2026-77933 since 08/21/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/20/2026). MITRE ATT&CK project uses the attack technique T1110.001 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• eosphoros-ai

Name

• DB-GPT

Version

• 0.8.0
• 0.8.1
• 0.8.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion