Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-51864 – Path Traversal Leading to Arbitrary File Write/RCE – DB-GPT v0.7.5 and v0.8.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-51864 is a critical path traversal vulnerability (CWE-22) in DB-GPT’s python_file_upload endpoint, affecting versions 0.7.5 and 0.8.0. An authenticated attacker can supply a crafted filename containing directory traversal sequences to write arbitrary Python files outside the intended upload directory, which can lead to remote code execution. The vulnerability carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: the POST /api/v1/python/upload endpoint (python_upload_api.py) uses the client-supplied file.filename from a multipart upload directly when writing to disk, without sanitizing directory traversal sequences (../) or validating that the resolved path stays within the designated upload directory.
  • The only validation performed on the uploaded filename is that it ends with a .py extension.
  • Trigger conditions: an attacker with a valid authentication token submits a file upload request with a filename such as ../../../../dbgpt/agent/backdoor.py, causing the server to write the file outside the intended workspace boundary.
  • Attack vector is network-based, requires low attack complexity, and no user interaction.
  • Impact: arbitrary file write to locations accessible by the DB-GPT application, which can be leveraged to plant Python files in locations later loaded/executed by the application, enabling code injection and persistent backdoors.

Affected software

  • DB-GPT (eosphoros-ai) version 0.7.5
  • DB-GPT (eosphoros-ai) version 0.8.0

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade DB-GPT to a version that includes the fix merged via the project’s corresponding pull request addressing the python_file_upload path traversal issue; confirm with the vendor that the patched release is applied.
  • If no patch can be applied immediately: restrict access to the /api/v1/python/upload endpoint to trusted users only, enforce strict filename validation/allow-listing at a reverse proxy or WAF layer to block path traversal sequences (../, absolute paths), and monitor the DB-GPT file storage directories for unexpected Python files written outside expected upload paths.
  • Review authentication and authorization controls for all file upload endpoints exposed by DB-GPT, since exploitation requires only a valid authenticated session token.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge