EUVD-2026-42116Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Network-reachable importer abused by an authenticated team member (PR:L), no interaction; SSRF reaches other systems (S:C) to disclose data (C:H) with no integrity or availability impact.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Lifecycle Timeline
2DescriptionCVE.org
FastGPT is a knowledge-based AI application platform. Prior to 4.15.0-beta4, the HTTP-tool OpenAPI schema importer validates only the top-level URL before passing it to SwaggerParser.bundle, whose remote reference resolver fetches $ref URLs without FastGPT's internal-address guard and returns fetched content inline, allowing an authenticated team member to read internal services or cloud metadata. This issue is fixed in version 4.15.0-beta4.
AnalysisAI
Server-side request forgery in FastGPT before 4.15.0-beta4 lets an authenticated team member abuse the HTTP-tool OpenAPI schema importer to reach internal-only services and cloud instance metadata. Because the importer only validates the top-level URL and then hands the document to SwaggerParser.bundle, whose $ref resolver fetches remote references without FastGPT's internal-address guard, fetched content is returned inline to the caller. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the vendor advisory (GHSA-72hf-5382-2mq9) confirms the flaw and its fix.
Technical ContextAI
The vulnerability lives in FastGPT's HTTP-tool feature, which imports OpenAPI/Swagger schemas so users can register external APIs as agent tools. FastGPT applies an internal-address SSRF guard to the top-level schema URL a user submits, but it then passes the document to the SwaggerParser.bundle() routine (from the swagger-parser/json-schema-ref-parser ecosystem). That library's remote reference resolver independently fetches any $ref that points to an external URL, and those secondary fetches bypass FastGPT's guard entirely, inlining the resolved response into the bundled schema returned to the user. This is a classic CWE-918 (SSRF) parser-side-effect: validation is applied to the request the developer expected (the top-level URL) but not to the transitive requests a downstream library performs on its behalf. The affected component is the labring/fastgpt application (cpe:2.3:a:labring:fastgpt:*).
RemediationAI
Vendor-released patch: 4.15.0-beta4 - upgrade FastGPT to 4.15.0-beta4 (or later) as described in advisory GHSA-72hf-5382-2mq9 (https://github.com/labring/FastGPT/security/advisories/GHSA-72hf-5382-2mq9); note this is a beta tag, so validate in staging before production rollout. Until you can upgrade, restrict who can use or configure the HTTP-tool OpenAPI schema importer by limiting team membership to trusted users, since the flaw requires an authenticated team account. As a network-layer compensating control, run FastGPT in a network segment that cannot reach cloud metadata endpoints (block egress to 169.254.169.254 and to internal service ranges via egress firewall or IMDSv2 hop-limit/session enforcement) - the trade-off is that any legitimate outbound API integrations FastGPT needs must be explicitly allowlisted. Avoid disabling outbound fetching wholesale if HTTP tools are relied upon operationally, as that breaks the feature.
FastGPT is an AI Agent building platform. Prior to version 4.9.12, the LastRoute Parameter on login page is vulnerable t
Unauthenticated HTTP proxy abuse in FastGPT (AI Agent platform) prior to v4.14.9.5 allows remote attackers to relay arbi
Remote code execution in FastGPT's agent-sandbox component (versions 4.14.10 through 4.14.12) lets any network-adjacent,
NoSQL injection in FastGPT <4.14.9.5 password authentication allows unauthenticated remote attackers to bypass login con
Channel hijack and denial of service in FastGPT (labring/FastGPT) before 4.15.2 lets an unauthenticated remote attacker
GitHub Actions artifact-poisoning (pwn request) in labring/FastGPT allows an external attacker who opens a pull request
NoSQL injection in FastGPT versions before 4.14.9.5 allows authenticated attackers to bypass password verification on th
Authentication bypass in FastGPT 4.15.0-beta4 lets unauthenticated remote attackers forge JWTs and access internal plugi
Cross-tenant file disclosure in FastGPT prior to v4.15.0-beta5 allows an attacker to read another team's stored files by
Server-Side Request Forgery in Labring FastGPT prior to 4.15.0-beta1 lets an authenticated attacker bypass the platform'
Server-side request forgery in FastGPT (labring) versions 4.14.11 and prior lets a low-privileged user coerce the server
Server-Side Request Forgery (SSRF) in FastGPT's Model Context Protocol (MCP) tools endpoints allows authenticated attack
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today