Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS v4.0 score of 5.3 reflects a Medium severity with network attack vector, low attack complexity, and low privilege requirements (authenticated user), but limited confidentiality impact and no integrity or availability impact in the base vector. The CVSS vector (AV:N/AC:L/PR:L) confirms unauthenticated users cannot exploit this-a valid team token is mandatory. However, the real-world risk is amplified in multi-tenant SaaS deployments: any paid subscriber or low-privileged user can systematically enumerate and access sensitive AI workflows, trained models, or configuration data of competing teams or organizations. The impact is primarily information disclosure (cross-tenant data exposure) and unauthorized execution of private workflows, making it a critical concern for data segregation compliance (SOC 2, ISO 27001). The availability of a patched version (4.14.10.4) and public GitHub advisory increases organizational visibility, reducing zero-day risk but elevating urgency for hosted instances. No EPSS score or KEV status provided; exploitation is straightforward (unauthenticated users are blocked, but any authenticated user can exploit), suggesting this will likely be actively exploited post-disclosure. |
| Exploit ScenarioDerived | An authenticated user or team in a FastGPT SaaS instance obtains or observes another team's application ID (e.g., via shared documentation, error messages, or brute-force enumeration). The attacker constructs an API request to read or execute that application while supplying their own valid team token. Because the API validates the team token but does not verify the application belongs to the team, the request succeeds, exposing the application's configuration, trained models, or execution results. No additional complexity or privilege escalation is required-the attacker simply needs a valid team account, making this a high-probability horizontal privilege escalation in multi-tenant deployments. No public exploit code has been identified as of this analysis, but the simplicity of the attack (direct object reference) and availability of public advisory details make rapid exploitation likely post-disclosure. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 10, 2026
Broken Access Control in FastGPT versions prior to 4.14.10.4 allows authenticated teams to access and execute applications belonging to other teams by supplying a foreign application ID, enabling cross-tenant data exposure and unauthorized workflow execution. The vulnerability stems from insufficient API validation-while team tokens are verified, the API fails to confirm that the requested application belongs to the authenticated team. This affects all FastGPT instances with multi-tenant deployments where different teams manage separate AI Agent applications, and is fixed in version 4.14.10.4.
RemediationAI
Upgrade FastGPT to version 4.14.10.4 or later immediately. The patched release is available at https://github.com/labring/FastGPT/releases/tag/v4.14.10.4 and includes API authorization logic that validates both team token ownership and application ownership before allowing access or execution. For organizations unable to upgrade immediately, implement network-level access controls to restrict API exposure to trusted internal networks or implement request-level rate limiting on application enumeration endpoints to reduce attack surface. Verify post-upgrade that API endpoints for executing or reading applications now properly reject cross-tenant requests with a 403 Forbidden response.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
FastGPT is a multi-tenant AI Agent building platform that uses team-based access control to isolate applications and workflows. The vulnerability is rooted in CWE-284 (Improper Access Control), specifically a horizontal privilege escalation pattern where API endpoints that accept an appId parameter perform team token validation but omit authorization checks to confirm the application belongs to the requesting team. This is a classic Broken Object Level Authorization (BOLA) or Insecure Direct Object Reference (IDOR) flaw common in REST APIs handling multi-tenant resources. The affected product is specified in CPE as cpe:2.3:a:labring:fastgpt:*:*:*:*:*:*:*:* for all versions prior to the patched release.
Know when Fastgpt gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N
Primary rating from Vendor (GitHub_M) · only source for this CVE.
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
FastGPT is an AI Agent building platform. Prior to 4.14.10.4, Broken Access Control vulnerability (IDOR/BOLA) allows any authenticated team to access and execute applications belonging to other teams by supplying a foreign appId. While the API correctly validates the team token, it does not verify that the requested application belongs to the authenticated team. This leads to cross-tenant data exposure and unauthorized execution of private AI workflows. This vulnerability is fixed in 4.14.10.4.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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
Authentication bypass in FastGPT 4.15.0-beta4 lets unauthenticated remote attackers forge JWTs and access internal plugi
NoSQL injection in FastGPT versions before 4.14.9.5 allows authenticated attackers to bypass password verification on th
FastGPT versions 4.14.8.3 and below contain a critical arbitrary code execution vulnerability in the fastgpt-preview-ima
Cross-tenant file disclosure in FastGPT prior to v4.15.0-beta5 allows an attacker to read another team's stored files by
Cross-tenant data disclosure in FastGPT 4.14.17 through 4.15.0-beta5 lets a low-privileged tenant user read another tena
Server-side request forgery in FastGPT before 4.15.0-beta4 lets an authenticated team member abuse the HTTP-tool OpenAPI
EUVD-2026-21605
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB