Live › vulnerability › CVE-2024-10833
Go to dashboardDB-GPT, an AI database assistant framework, builds the storage path for uploaded knowledge documents from the user-supplied filename, so absolute paths are accepted. An attacker who can reach the upload endpoint can write files to arbitrary locations on the server, which can lead to code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 16:25 UTC, 0h before NVD. All times on this page are UTC.
Teams running the dbgpt Python package before 0.6.2 that expose its knowledge API. The flaw sits in the document upload path, so instances that do not use the knowledge upload feature or keep the API off the network are lower risk. Teams on 0.6.2 or later are not affected.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| dbgpt | pypi | < 0.6.2 | 0.6.2 |
| dbgpt db-gpt | vendor | = 0.6.0 | – |
pip show dbgpt and confirm the installed version is below 0.6.2.knowledge/{space_name}/document/upload is reachable from untrusted networks.dbgpt PyPI package to 0.6.2 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2024-10833")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.