Summary
CVE-2026-73034 is an unauthenticated path traversal vulnerability (CWE-22) in DB-GPT, an open-source AI-powered database interaction platform maintained by eosphoros-ai. The flaw resides in the Python file-upload endpoint, where a client-supplied user_id HTTP header is used, unvalidated, to build the upload directory path, allowing attackers to write arbitrary files outside the intended directory and potentially achieve remote code execution. The issue is rated CRITICAL with a CVSS v4.0 base score of 9.3 (CVSS v3.1: 9.8).
Technical details
- Root cause: The upload handler builds the destination directory as
os.path.join(base_dir, "python_uploads", user_id), whereuser_idis taken directly from an HTTP header without sanitization or path-containment checks. - Trigger condition: An attacker sends a multipart file-upload request to the Python upload endpoint with a
user_idheader containing directory traversal sequences (e.g.../../), causing the server to write the uploaded file outside the intendedpython_uploadsdirectory. - Attack vector: Network-based, unauthenticated, no user interaction required.
- Impact: Arbitrary file write to attacker-chosen locations on the server filesystem. Depending on server configuration, this can be leveraged to overwrite startup hooks, cron entries, or agent script files, leading to remote code execution, alongside full loss of confidentiality, integrity, and availability.
Affected software
- DB-GPT (eosphoros-ai), versions 0 through 0.8.1 (inclusive)
Severity
- CVSS v3.1: 9.8 (Critical) —
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS v4.0: 9.3 (Critical) —
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: Upgrade DB-GPT to a version incorporating the fix applied in commit
e0c741bd2b5e521b128cffb3f68982dde3f7b359, which validatesuser_idagainst an alphanumeric/underscore/hyphen-only pattern and enforces path-containment checks (including TOCTOU/symlink protections) before writing uploaded files. - If immediate patching is not possible: Restrict network exposure of the DB-GPT file-upload endpoint (e.g. place it behind authentication, a VPN, or an allow-list at the network layer), and monitor for file-upload requests containing traversal sequences (
../) in theuser_idheader.

