---
id: "CVE-2026-51863"
kind: "vulnerability"
aliases: ["CVE-2026-51863"]
title: "DB-GPT: directory traversal lets remote users write files outside workspace"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: [{"name": "DB-GPT", "fixed": [], "affected": "0.7.5, 0.8.0", "ecosystem": "pip"}]
ecosystems: []
tags: ["ai-tooling", "db-gpt", "python", "self-hosted"]
not_affected_if: ["api-not-exposed", "other-versions"]
published_at: "2026-10-29T18:17:32+00:00"
first_seen_at: "2026-10-29T18:26:33+00:00"
updated_at: "2026-10-29T18:30:51+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-51863", "first_seen_at": "2026-10-29T18:26:33+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-10-29T18:30:51+00:00"}]
---

# DB-GPT: directory traversal lets remote users write files outside workspace

DB-GPT versions 0.7.5 and 0.8.0 have a directory traversal flaw in the use_example_file function of its examples API. A remote attacker can write files outside the intended workspace or storage directory.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- pip:DB-GPT affected 0.7.5, 0.8.0 fixed ?

## How to check

- Check the installed DB-GPT version (`dbgpt --version` or the package version in `packages/dbgpt-app`) and see whether it is `0.7.5` or `0.8.0`.
- Look at `packages/dbgpt-app/src/dbgpt_app/openapi/api_v1/examples_api.py` around line 129 to confirm the file-path handling in `use_example_file`.

## Timeline

- 2026-10-29T18:26:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-51863
- 2026-10-29T18:30:51+00:00 analyst — Reporter issue #3028 (closed; referenced by PR #3066 'validate example file names') shows the traversal is via example['name'] from the EXAMPLE_FILES dict, not a request parameter; endpoint POST /api/v1/examples/use needs the user_id header dependency (which sibling CVEs say is a mock granting admin). The issue's PoC requires tampering with EXAMPLE_FILES, so practical exploitability looks low. No vendor advisory or fixed release found; PR page unreadable, so the fix version is unknown. Severity left unchanged. Settle it by checking whether PR #3066 is merged and which release contains it.

## Documents

- [describes] DB-GPT #3028 Path Traversal in use_example_file (closed, ref PR #3066) https://github.com/eosphoros-ai/DB-GPT/issues/3028
- [mentions] DB-GPT CVE history (Release Alert) https://releasealert.dev/github/eosphoros-ai/DB-GPT/cves

## From the sources

DB-GPT v0.7.5 and 0.8.0 contains directory traversal in use_example_file (packages/dbgpt-app/src/dbgpt_app/openapi/api_v1/examples_api.py:129). A remote attacker can use the validated exploitation path to write files outside the intended workspace or storage boundary.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_
