DB-GPT v0.8.0 sandbox API silently falls back to LocalRuntime and executes code on host.
Summary
DB-GPT v0.8.0 sandbox API silently falls back to LocalRuntime and executes code on host.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2026-51869 was discovered in DB-GPT v0.8.0 sandbox API.
Severity is Critical (CVSS 9.8/10). If exploited, attackers can fully take over the affected system.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "DB-GPT v0.8.0 sandbox API CVE-2026-51869".
CVE-2026-51869 (DB-GPT v0.8.0 sandbox API). Severity: Critical / CVSSv3 9.8. Category: CWE-284.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2026-51869) in DB-GPT v0.8.0 sandbox API. A serious software flaw has been identified.
Target versions of DB-GPT v0.8.0 sandbox API (see vendor advisory). If running in production, identify exposure immediately.
Severity: Critical (CVSS 9.8/10). If exploited, attackers can fully take over the affected system.
Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-284)
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
References
- web gist.github.com
- web github.com
- web nvd.nist.gov
- web github.com