# CVE-2026-73034: DB-GPT v0.8.1 Path Traversal Arbitrary File Write via user_id Header

> Remote attackers can write arbitrary files via path traversal in the user_id header, leading to remote code execution on DB-GPT servers.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-v6p5-5pcg-cr3f

## What is CVE-2026-73034?

CVE-2026-73034 is a critical path traversal vulnerability in eosphoros-ai DB-GPT, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-73034?


## How do I fix CVE-2026-73034?

No fix has been published for CVE-2026-73034 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73034 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73034 exists.

Public exploit code:

- CVE-2026-73034 — DB-GPT v0.8.1 unauth path traversal → arbitrary file write as root via user-id header. Verified + fix diff (github_poc): https://github.com/Boreas37/CVE-2026-73034-PoC
- DB-GPT <= 0.8.1 - Arbitrary File Write (nuclei): http/cves/2026/CVE-2026-73034.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73034 and fix it if it is affected.

What it is: CVE-2026-73034 is a critical path traversal vulnerability in eosphoros-ai DB-GPT, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73034 exists.

Affected product: eosphoros-ai DB-GPT. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73034/ (Markdown: https://insights.sbomify.com/CVE-2026-73034/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73034
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73034
- OSV: https://osv.dev/vulnerability/CVE-2026-73034

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73034/
Summaries are generated and may contain mistakes; the official description above is the record.