# CVE-2026-77932: DB-GPT through 0.8.2 Unauthenticated RCE via /api/v1/chat/react-agent


- **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
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-5vjv-vw3m-qpqp

## What is CVE-2026-77932?

CVE-2026-77932 is a critical vulnerability in eosphoros-ai DB-GPT, published on 20 Oct 2026. 

### Official description

DB-GPT through 0.8.2 contains an unauthenticated remote code execution vulnerability because the /api/v1/chat/react-agent endpoint relies on a mock get_user_from_headers function that grants every caller the admin role. Unauthenticated attackers can send prompts that make the ReAct agent's unsandboxed code_interpreter and shell_interpreter tools run arbitrary Python or bash as root in the webserver container, including reaching the bundled database with default credentials.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-77932 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77932 is a critical vulnerability in eosphoros-ai DB-GPT, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77932 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-77932/ (Markdown: https://insights.sbomify.com/CVE-2026-77932/index.md)
```

## Sources

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

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