CVE-2026-44284: labring FastGPT · Server-Side Request Forgery (SSRF)
Affects labring FastGPTSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.14.17 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.14.17
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade FastGPT and labring/FastGPT to 4.14.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| labringFastGPT | Affected
| Fixed in
|
GitHublabring/FastGPTpkg:github/labring/FastGPTOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade FastGPT to version 4.14.17 or later, where this SSRF vulnerability has been patched. Since this is not a cloud service, users must apply the update themselves. Patch status is not explicitly stated beyond the version fix, so verify with the vendor for any additional guidance.
Description
FastGPT is an AI Agent building platform. Prior to version 4.14.17, FastGPT had an inconsistent SSRF protection gap in MCP tool URL handling. The direct MCP preview/run endpoints already rejected internal/private network URLs, but the MCP tool create/update endpoints could still save an internal MCP server URL. That stored URL could later be used by workflow execution without revalidating the destination. An authenticated user with permission to create or manage MCP toolsets could store an internal endpoint such as http://localhost:3000/mcp and later cause the FastGPT backend workflow runner to connect to that internal destination. This issue has been patched in version 4.14.17.
References
- github.com/labring/FastGPT/security/advisories/GHSA-cxxj-99f7-f5wq (opens in a new tab)
- github.com/labring/FastGPT/pull/6826 (opens in a new tab)
- github.com/labring/FastGPT/commit/c1c6b9520d976d25ed945b5bc4e0768149e6db69 (opens in a new tab)
- github.com/labring/FastGPT/releases/tag/v4.14.17 (opens in a new tab)