<?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/"><channel><title>FastGPT — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/fastgpt/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Sat, 18 Apr 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/fastgpt/feed.xml" rel="self" type="application/rss+xml"/><item><title>FastGPT NoSQL Injection Vulnerability (CVE-2026-40351)</title><link>https://feed.craftedsignal.io/briefs/2026-04-fastgpt-nosql-injection/</link><pubDate>Sat, 18 Apr 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-fastgpt-nosql-injection/</guid><description>FastGPT versions before 4.14.9.5 are vulnerable to NoSQL injection, allowing unauthenticated attackers to bypass authentication and gain administrative access.</description><content:encoded><![CDATA[<p>FastGPT is an AI Agent building platform. Versions prior to 4.14.9.5 are susceptible to a critical NoSQL injection vulnerability (CVE-2026-40351) affecting the password-based login endpoint. The vulnerability stems from the use of TypeScript type assertion without runtime validation, enabling unauthenticated attackers to inject MongoDB query operators within the password field. This bypasses the intended password check, granting the attacker the ability to authenticate as any user, including the root administrator. Successful exploitation leads to complete control over the FastGPT instance and its associated data. This vulnerability was addressed in FastGPT version 4.14.9.5. All users of FastGPT versions prior to 4.14.9.5 are vulnerable to this attack.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker identifies a vulnerable FastGPT instance running a version prior to 4.14.9.5.</li>
<li>The attacker crafts a malicious HTTP POST request to the password-based login endpoint.</li>
<li>Within the POST request body, the attacker places a MongoDB query operator object (e.g., <code>{&quot;$ne&quot;: &quot;&quot;}</code>) in the password field, bypassing the standard password check.</li>
<li>The vulnerable FastGPT application processes the malicious request without proper validation.</li>
<li>The MongoDB query operator is executed, bypassing the authentication mechanism.</li>
<li>The attacker is granted unauthorized access to the FastGPT application, assuming the identity of an arbitrary user, including the root administrator.</li>
<li>The attacker leverages their administrative privileges to access sensitive data, modify configurations, or perform other malicious actions within the FastGPT instance.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-40351 allows an unauthenticated attacker to gain complete control over a FastGPT instance. This can lead to unauthorized access to sensitive AI agent configurations, user data, and other critical information. The impact includes data breaches, service disruption, and potential compromise of downstream systems that rely on the FastGPT platform. Given the critical nature of AI agent building platforms, the compromise of a FastGPT instance can have far-reaching consequences.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately upgrade all FastGPT instances to version 4.14.9.5 or later to patch CVE-2026-40351.</li>
<li>Deploy the Sigma rule <code>Detect FastGPT NoSQL Injection Attempt</code> to identify potential exploitation attempts targeting the login endpoint.</li>
<li>Monitor web server logs for unusual POST requests to the login endpoint, specifically looking for MongoDB query operators within the password field as detected by rule <code>Detect FastGPT NoSQL Injection Attempt</code>.</li>
<li>Review and restrict network access to the FastGPT instance to only authorized users and systems to minimize the attack surface.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>NoSQL injection</category><category>authentication bypass</category><category>CVE-2026-40351</category><category>FastGPT</category></item><item><title>FastGPT NoSQL Injection Vulnerability in Password Change Endpoint</title><link>https://feed.craftedsignal.io/briefs/2026-04-fastgpt-nosql/</link><pubDate>Fri, 17 Apr 2026 22:16:32 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-fastgpt-nosql/</guid><description>FastGPT versions prior to 4.14.9.5 are vulnerable to NoSQL injection in the password change endpoint, allowing authenticated attackers to bypass password verification and perform account takeover.</description><content:encoded><![CDATA[<p>FastGPT, an AI Agent building platform, is susceptible to a critical NoSQL injection vulnerability affecting versions before 4.14.9.5. The flaw resides within the password change endpoint, enabling an authenticated attacker to circumvent the necessary &ldquo;old password&rdquo; verification process. By injecting MongoDB query operators, an attacker with an existing, low-privileged session can manipulate password changes for their own account, or potentially other accounts if combined with ID manipulation techniques. This exploit leads to full account takeover, allowing attackers to maintain persistence and potentially compromise sensitive data. This vulnerability has been patched in version 4.14.9.5, urging users to upgrade immediately.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains initial access to a FastGPT account with low privileges through legitimate means (e.g., registration or stolen credentials).</li>
<li>Attacker navigates to the password change endpoint within the FastGPT application.</li>
<li>The attacker crafts a malicious request to the password change endpoint, injecting MongoDB query operators into the &ldquo;old password&rdquo; field. For example, using a payload like <code>{$ne: &quot;legitimate_old_password&quot;}</code>.</li>
<li>The application&rsquo;s backend improperly processes the injected query operators, failing to correctly validate the old password against the stored hash.</li>
<li>The attacker provides a new password and confirms it within the crafted request.</li>
<li>The FastGPT application updates the account&rsquo;s password in the database, replacing the original password with the attacker-controlled value.</li>
<li>The attacker logs out and logs back in using the newly set password, gaining full control of the compromised account.</li>
<li>The attacker leverages the compromised account to access sensitive data, modify configurations, or perform other malicious activities within the FastGPT platform.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows attackers to take complete control of FastGPT accounts. The consequences range from unauthorized access to sensitive data and configurations to potential manipulation of AI agent behavior. This account takeover can lead to data breaches, service disruption, and reputational damage. While the specific number of victims is unknown, any FastGPT instance running a version prior to 4.14.9.5 is vulnerable, potentially affecting a wide range of users and organizations. The CVSS v3.1 base score of 8.8 highlights the severity of this issue.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately upgrade all FastGPT installations to version 4.14.9.5 or later to patch the NoSQL injection vulnerability (CVE-2026-40352).</li>
<li>Implement the Sigma rule <code>Detect FastGPT Password Reset Bypass</code> to detect potential exploitation attempts against the password change endpoint.</li>
<li>Review FastGPT webserver logs for unusual patterns or MongoDB query operators within requests to the password change endpoint to identify potential compromises.</li>
<li>Enable and review detailed webserver logging for FastGPT to increase visibility into HTTP requests.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>nosql-injection</category><category>account-takeover</category><category>cve</category><category>fastgpt</category><category>privilege-escalation</category></item><item><title>Critical Vulnerability in FastGPT Allows API Key Exfiltration and Internal Network Access</title><link>https://feed.craftedsignal.io/briefs/2026-04-fastgpt-vuln/</link><pubDate>Wed, 01 Apr 2026 16:12:02 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-fastgpt-vuln/</guid><description>CVE-2026-34162 in FastGPT allows unauthenticated attackers to exfiltrate API keys and gain complete access to internal services managed by Docker Compose by sending arbitrary HTTP requests, leading to potential compromise of the internal network.</description><content:encoded><![CDATA[<p>A critical vulnerability, CVE-2026-34162, has been identified in FastGPT, a framework for building AI-powered applications. The vulnerability resides in the HTTP tools testing endpoint, which is accessible without authentication. This allows an unauthenticated attacker to send arbitrary server-side HTTP requests and receive the responses. If the default admin token is not changed, an attacker can access the proxy management API to exfiltrate third-party API keys. Furthermore, the attacker can interact with and potentially exploit all Docker Compose internal services by manipulating HTTP headers. This issue was publicly disclosed on April 1, 2026, by CCB Belgium, who strongly recommends immediate patching. The vulnerability is patched in version 4.14.9.5. Successful exploitation can lead to complete control over the internal network and sensitive data exposure.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An unauthenticated attacker identifies a vulnerable FastGPT instance exposed to the network.</li>
<li>The attacker accesses the FastGPT HTTP tools testing endpoint without authentication.</li>
<li>The attacker uses the endpoint to send arbitrary HTTP requests to the FastGPT server itself or internal services.</li>
<li>If the default admin token is unchanged, the attacker uses the HTTP proxy functionality to access the proxy management API.</li>
<li>The attacker exfiltrates third-party API keys stored within the FastGPT configuration.</li>
<li>The attacker leverages the exfiltrated API keys to access external services, potentially causing further damage.</li>
<li>The attacker uses the HTTP proxy functionality, including custom headers, to interact with other Docker Compose internal services.</li>
<li>The attacker exploits vulnerabilities in these internal services, leading to complete access to the internal network and sensitive data.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-34162 can lead to the complete compromise of the FastGPT server and the internal network it manages. An attacker can exfiltrate sensitive API keys, gain unauthorized access to internal services, and potentially pivot to other systems within the network. The vulnerability poses a high risk to the confidentiality and integrity of data, potentially impacting numerous organizations relying on FastGPT for their AI-powered applications. The CCB Belgium advisory highlights the potential for widespread impact given the nature of the vulnerability and the popularity of FastGPT.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately patch FastGPT instances to version 4.14.9.5 to remediate CVE-2026-34162 as per the vendor advisory.</li>
<li>Implement the remediations documented in the vendor advisory to strengthen the security of FastGPT instances.</li>
<li>Upscale monitoring and detection capabilities to identify any related suspicious activity, ensuring a swift response in case of an intrusion, as recommended by the CCB.</li>
<li>Investigate and report any suspected intrusions using the incident reporting URL found in the advisory (<a href="https://ccb.belgium.be/report-incident)">https://ccb.belgium.be/report-incident)</a>.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>fastgpt</category><category>vulnerability</category><category>information-disclosure</category></item></channel></rss>