CVE-2026-54601
Received Received - Intake

Authentication Bypass in FastGPT via Dataset ID Manipulation

Vulnerability report for CVE-2026-54601, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-07

Last updated on: 2026-07-07

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-07
Last Modified
2026-07-07
Generated
2026-07-08
AI Q&A
2026-07-08
EPSS Evaluated
N/A
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
fastgpt fastgpt From 4.14.17 (inc) to 4.15.0-beta4 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-915 The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in FastGPT, an open source AI knowledge base platform, in versions from 4.14.17 to before 4.15.0-beta4. It allows an authenticated tenant user to call a specific API endpoint (POST /api/core/dataset/collection/create/reTrainingCollection) in a way that causes a server-owned datasetId from another tenant to be persisted. This results in mixed dataset objects where ownership is inconsistent, leading to authorization decisions based on incorrect ownership information.

Because of this, users can gain cross-tenant access to read, update, and delete datasets, collections, and training data if they know the mixed object IDs. The issue was fixed in version 4.15.0-beta4.

Impact Analysis

This vulnerability can impact you by allowing unauthorized access across tenants within the FastGPT platform. Specifically, an authenticated user from one tenant can read, modify, or delete datasets, collections, and training data belonging to another tenant if they know the relevant object IDs.

Such unauthorized cross-tenant access can lead to data leakage, data corruption, and loss of data integrity, potentially compromising the confidentiality, integrity, and availability of your data.

Mitigation Strategies

To mitigate this vulnerability, you should upgrade FastGPT to version 4.15.0-beta4 or later, where the issue is fixed.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54601. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart