EUVD-2026-42114Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Network-accessible API requiring authenticated tenant (PR:L); S:U retained as cross-tenant impact stays within the FastGPT application boundary; C/I/A:L reflects partial data access across tenant lines.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
FastGPT is an open source AI knowledge base platform. From 4.14.17 to before 4.15.0-beta4, FastGPT allows an authenticated tenant user to call POST /api/core/dataset/collection/create/reTrainingCollection in a way that persists a server-owned datasetId value from another tenant. This creates mixed dataset objects and downstream dataset, collection, and training endpoints then make authorization decisions from inconsistent ownership anchors, allowing cross-tenant read, update, and delete access when mixed object ids are known. This issue is fixed in version 4.15.0-beta4.
AnalysisAI
Cross-tenant authorization bypass in FastGPT (versions 4.14.17 through pre-4.15.0-beta4) permits an authenticated tenant user to inject a foreign tenant's datasetId via the POST /api/core/dataset/collection/create/reTrainingCollection endpoint, corrupting ownership anchors in persisted dataset objects. Downstream dataset, collection, and training endpoints then derive authorization decisions from these poisoned records, granting the attacker cross-tenant read, update, and delete access to another tenant's data. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; the vendor released version 4.15.0-beta4 as the confirmed fix.
Technical ContextAI
FastGPT is an open-source AI knowledge base platform (CPE: cpe:2.3:a:labring:fastgpt) that supports multi-tenant deployments where datasets, collections, and training jobs are scoped by tenant ownership. The root cause is CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes), commonly known as mass assignment: the reTrainingCollection API endpoint accepts a client-supplied datasetId field without enforcing that it belongs to the requesting tenant's security boundary. Once this foreign identifier is written to the datastore, all downstream authorization logic - across the dataset, collection, and training API surfaces - reads the corrupted ownership record and evaluates permissions against the wrong tenant anchor. The vulnerability is not in a parsing or memory-handling layer but in the application's trust model for incoming object attributes at a privileged API endpoint.
RemediationAI
Upgrade to FastGPT version 4.15.0-beta4 or later; the patched release is available at https://github.com/labring/FastGPT/releases/tag/v4.15.0-beta4 and the fix was introduced via pull request #7071 (commit 54a53e7d4399f1dfa2913394442c3cf6de672fb3). If an immediate upgrade is not feasible, restrict access to the POST /api/core/dataset/collection/create/reTrainingCollection endpoint at the network or API gateway layer so that only internal or trusted network segments can reach it - this eliminates the attack surface but will disable re-training collection workflows for affected users. Additionally, audit existing collection records for datasetId values that do not match the owning tenant to detect any prior exploitation; inconsistencies indicate mixed-ownership objects that should be remediated by reassigning or purging the affected records.
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
FastGPT versions 4.14.8.3 and below contain a critical arbitrary code execution vulnerability in the fastgpt-preview-ima
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 FastGPT before 4.15.0-beta4 lets an authenticated team member abuse the HTTP-tool OpenAPI
Server-Side Request Forgery in Labring FastGPT prior to 4.15.0-beta1 lets an authenticated attacker bypass the platform'
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today