Dbgpt Db Gpt
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Dbgpt Db Gpt.
By the Year
In 2026 there have been 4 vulnerabilities in Dbgpt Db Gpt with an average score of 9.3 out of ten. Last year, in 2025 Db Gpt had 10 security vulnerabilities published. Right now, Db Gpt is on track to have less security vulnerabilities in 2026 than it did last year. However, the average CVE base score of the vulnerabilities in 2026 is greater by 0.07.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 4 | 9.30 |
| 2025 | 10 | 9.23 |
It may take a day or so for new Db Gpt vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Dbgpt Db Gpt Security Vulnerabilities
DB-GPT 0.8.2 Hardcoded MYSQL_ROOT_PASSWORD in docker-compose.yml Exposes Port 3306
CVE-2026-77933
9.3 - Critical
- October 20, 2026
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.
1392
DB-GPT 0.8.2 RCE via /api/v1/chat/react-agent (admin bypass)
CVE-2026-77932
9.3 - Critical
- October 20, 2026
DB-GPT through 0.8.2 contains an unauthenticated remote code execution vulnerability because the /api/v1/chat/react-agent endpoint relies on a mock get_user_from_headers function that grants every caller the admin role. Unauthenticated attackers can send prompts that make the ReAct agent's unsandboxed code_interpreter and shell_interpreter tools run arbitrary Python or bash as root in the webserver container, including reaching the bundled database with default credentials.
Missing Authentication for Critical Function
Dir Traversal + Code Exec in DB-GPT Upload API
CVE-2026-80104
9.3 - Critical
- August 25, 2026
DB-GPT builds the destination path for an uploaded skill from the multipart filename without constraining it to the upload directory. skill_upload in packages/dbgpt-app/src/dbgpt_app/openapi/api_v1/agentic_data_api.py takes file.filename as given and writes the request body to upload_dir / filename. A path composed with that operator discards the left operand when the right one is absolute and follows parent references otherwise, so a filename such as ../../../tmp/x or /tmp/x resolves outside the intended directory; nothing canonicalises the result, checks that it remains under the upload root, or prevents a .py suffix. The route's only dependency is get_user_from_headers in dbgpt_serve/utils/auth.py, which returns a request carrying the admin role whether or not a user_id header is supplied, so the endpoint is reachable without credentials. A remote attacker holding no account can therefore write attacker-controlled bytes to any path the server process can write, place a new Python module inside the application package or replace one the application already imports, and obtain code execution in the server process when that module is next imported.
Directory traversal
DB-GPT v0.8.1 Unauthenticated Path Traversal via user_id Header
CVE-2026-73034
9.3 - Critical
- August 11, 2026
DB-GPT v0.8.1 contains an unauthenticated path traversal vulnerability that allows remote attackers to write arbitrary files to any location on the server by injecting directory traversal sequences into the user_id HTTP header of the Python file-upload endpoint. Attackers can send a crafted multipart upload request with a traversal-poisoned user_id header to escape the intended upload directory and write attacker-controlled content to locations such as Python startup hooks, cron directories, or agent scripts, resulting in remote code execution.
Directory traversal
DB-GPT Arbitrary File Deletion via Unvalidated Backslash in /v1/agent/hub/update
CVE-2025-0452
- March 20, 2025
eosphoros-ai/DB-GPT version latest is vulnerable to arbitrary file deletion on Windows systems via the '/v1/agent/hub/update' endpoint. The application fails to properly filter the '\' character, which is commonly used as a separator in Windows paths. This vulnerability allows attackers to delete any files on the host system by manipulating the 'plugin_repo_name' variable.
External Control of File Name or Path
CORS CSRF in eosphoros-ai/db-gpt 0.6.0 Due to Oversized CORSMiddleware
CVE-2024-10906
8.1 - High
- March 20, 2025
In version 0.6.0 of eosphoros-ai/db-gpt, the `uvicorn` app created by `dbgpt_server` uses an overly permissive instance of `CORSMiddleware` which sets the `Access-Control-Allow-Origin` to `*` for all requests. This configuration makes all endpoints exposed by the server vulnerable to Cross-Site Request Forgery (CSRF). An attacker can exploit this vulnerability to interact with any endpoints of the instance, even if the instance is not publicly exposed to the network.
Session Riding
Arbitrary File Upload in eosphoros-ai/db-gpt v0.6.0 via /v1/personal/agent/upload
CVE-2024-10902
- March 20, 2025
In eosphoros-ai/db-gpt version v0.6.0, the web API `POST /v1/personal/agent/upload` is vulnerable to Arbitrary File Upload with Path Traversal. This vulnerability allows unauthorized attackers to upload arbitrary files to the victim's file system at any location. The impact of this vulnerability includes the potential for remote code execution (RCE) by writing malicious files, such as a malicious `__init__.py` in the Python's `/site-packages/` directory.
Directory traversal
db-gpt v0.6.0 Unrestricted SQL exec Enables RCE via AFW
CVE-2024-10901
9.8 - Critical
- March 20, 2025
In eosphoros-ai/db-gpt version v0.6.0, the web API `POST /api/v1/editor/chart/run` allows execution of arbitrary SQL queries without any access control. This vulnerability can be exploited by attackers to perform Arbitrary File Write, enabling them to write arbitrary files to the victim's file system. This can potentially lead to Remote Code Execution (RCE) by writing malicious files such as `__init__.py` in the Python's `/site-packages/` directory.
Unrestricted File Upload
Arbitrary SQL Exec & RCE in eosphoros-ai/db-gpt v0.6.0 via /api/sql/run
CVE-2024-10835
9.8 - Critical
- March 20, 2025
In eosphoros-ai/db-gpt version v0.6.0, the web API `POST /api/v1/editor/sql/run` allows execution of arbitrary SQL queries without any access control. This vulnerability can be exploited by attackers to perform Arbitrary File Write using DuckDB SQL, enabling them to write arbitrary files to the victim's file system. This can potentially lead to Remote Code Execution (RCE).
SQL Injection
db-gpt 0.6.0 Arbitrary File Write via RAG-knowledge Endpoint
CVE-2024-10834
- March 20, 2025
eosphoros-ai/db-gpt version 0.6.0 contains a vulnerability in the RAG-knowledge endpoint that allows for arbitrary file write. The issue arises from the ability to pass an absolute path to a call to `os.path.join`, enabling an attacker to write files to arbitrary locations on the target server. This vulnerability can be exploited by setting the `doc_file.filename` to an absolute path, which can lead to overwriting system files or creating new SSH-key entries.
External Control of File Name or Path
Arbitrary File Write via Knowledge API in db-gpt 0.6.0
CVE-2024-10833
- March 20, 2025
eosphoros-ai/db-gpt version 0.6.0 is vulnerable to an arbitrary file write through the knowledge API. The endpoint for uploading files as 'knowledge' is susceptible to absolute path traversal, allowing attackers to write files to arbitrary locations on the target server. This vulnerability arises because the 'doc_file.filename' parameter is user-controllable, enabling the construction of absolute paths.
Absolute Path Traversal
eosphoros-ai/db-gpt v0.6.0 absolute path traversal via file upload
CVE-2024-10831
- March 20, 2025
In eosphoros-ai/db-gpt version 0.6.0, the endpoint for uploading files is vulnerable to absolute path traversal. This vulnerability allows an attacker to upload arbitrary files to arbitrary locations on the target server. The issue arises because the `file_key` and `doc_file.filename` parameters are user-controllable, enabling the construction of paths outside the intended directory. This can lead to overwriting essential system files, such as SSH keys, for further exploitation.
Absolute Path Traversal
eosphoros-ai/db-gpt 0.6.0 Path Traversal Deletion API
CVE-2024-10830
- March 20, 2025
A Path Traversal vulnerability exists in the eosphoros-ai/db-gpt version 0.6.0 at the API endpoint `/v1/resource/file/delete`. This vulnerability allows an attacker to delete any file on the server by manipulating the `file_key` parameter. The `file_key` parameter is not properly sanitized, enabling an attacker to specify arbitrary file paths. If the specified file exists, the application will delete it.
Directory traversal
DoS via Multipart Boundary in eosphoros-ai/db-gpt v0.6.0
CVE-2024-10829
- March 20, 2025
A Denial of Service (DoS) vulnerability in the multipart request boundary processing mechanism of eosphoros-ai/db-gpt v0.6.0 allows unauthenticated attackers to cause excessive resource consumption. The server fails to handle excessive characters appended to the end of multipart boundaries, leading to an infinite loop and complete denial of service for all users. This vulnerability affects all endpoints processing multipart/form-data requests.
Infinite Loop
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Dbgpt Db Gpt or by Dbgpt? Click the Watch button to subscribe.
