<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>DB-GPT - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/db-gpt/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 20 Oct 2026 02:31:34 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/db-gpt/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Unauthenticated RCE in DB-GPT via Insecure Mock Authentication</title><link>https://feed.craftedsignal.io/briefs/2026-10-db-gpt-rce/</link><pubDate>Tue, 20 Oct 2026 02:31:34 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-db-gpt-rce/</guid><description>DB-GPT versions 0.8.2 and earlier contain an unauthenticated remote code execution vulnerability in the ReAct agent endpoint that allows attackers to execute arbitrary system commands as root.</description><content:encoded><![CDATA[<p>DB-GPT versions through 0.8.2 are vulnerable to an unauthenticated remote code execution (RCE) flaw originating from an insecure implementation of the <code>get_user_from_headers</code> function. This function serves as a mock authentication mechanism, incorrectly assigning the &quot;admin&quot; role to every incoming request regardless of provided headers.</p>
<p>The vulnerability is exposed via the <code>/api/v1/chat/react-agent</code> endpoint. Attackers can leverage this misconfiguration to interact with the ReAct agent, specifically utilizing the <code>code_interpreter</code> and <code>shell_interpreter</code> tools. Because these tools operate in an unsandboxed environment within the webserver container, they permit the execution of arbitrary Python or bash commands with root-level privileges. An attacker successful in exploiting this vulnerability can gain full control over the container, access sensitive application data, or interact with the bundled database using default administrative credentials.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation results in full remote code execution within the DB-GPT webserver container. Attackers can achieve complete system compromise, exfiltrate data from the bundled database, or move laterally if the container lacks sufficient network segmentation. This vulnerability is particularly critical for deployments exposed to untrusted networks.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately upgrade to a patched version of DB-GPT that addresses CVE-2026-77932 and removes the mock <code>get_user_from_headers</code> function.</li>
<li>Restrict network access to the <code>/api/v1/chat/react-agent</code> endpoint to authorized internal segments only using a Web Application Firewall (WAF) or ingress controller rules.</li>
<li>Audit logs for suspicious HTTP POST requests directed at <code>/api/v1/chat/react-agent</code> containing shell metacharacters or unauthorized Python code patterns.</li>
<li>Implement strict resource limits and user privilege isolation for the DB-GPT container to minimize the impact of a potential container breakout or compromise.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>remote-code-execution</category><category>web-application</category><category>container-security</category><category>vulnerability</category><category>credential-exposure</category><category>mysql</category></item></channel></rss>