Description
FastGPT is an open source AI knowledge base platform. Prior to v4.15.0-beta5, two FastGPT file handlers authorize an unrelated resource and then sign or read an S3 object using a key taken directly from the request, without checking that the key belongs to the caller's team. Because S3 object keys are global within the bucket and carry the tenant id only as a path segment, an attacker can supply another team's key and obtain its file contents through the chat-file presign endpoint or dataset preview endpoint. This issue is fixed in version v4.15.0-beta5.
Published: 2026-07-07
Score: 8.6 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

FastGPT’s S3 presign and read handlers do not verify that the S3 key supplied in an HTTP request belongs to the caller’s team. Because the bucket stores tenant identifiers only as part of the key path, an attacker can supply another team’s key and obtain its file contents through the chat‑file presign or dataset preview endpoints. (CWE‑639) leads to cross‑team file disclosure and compromises confidentiality. Based on the description, it is inferred that the attack requires only the ability to send an HTTP request to the affected endpoints with a maliciously chosen key; no additional privileges are needed.

Affected Systems

The vulnerable component is FastGPT, an open‑source AI knowledge base platform developed by labring. All releases earlier than v4.15.0‑beta5 are affected; the flaw exists in the chat‑file presign endpoint and the dataset preview endpoint of those versions.

Risk and Exploitability

The vulnerability has a CVSS score of 8.6, indicating high severity. The EPSS score is < 1%, meaning a low but nonzero likelihood FastGPT is not listed in CISA’s KEV catalog. Because the bucket is shared globally and the key is a global identifier, an attacker who can send an HTTP request can potentially read files belonging to any team, leading to widespread data leakage. The exploitation path requires only the ability to craft a request with a target key.

Generated by OpenCVE AI on July 25, 2026 at 20:52 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade FastGPT to v4.15.0‑beta5 or later, where the key binding enforcement has been implemented.
  • Apply strict S3 bucket policies that restrict read access to objects belonging to the requesting team, preferably using IAM conditions that validate the team identifier in the key path.
  • Modify the chat‑file presign and dataset preview endpoints to validate that the requested S3 key belongs to the requesting user’s team before generating a presigned URL.

Generated by OpenCVE AI on July 25, 2026 at 20:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 09 Jul 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 07 Jul 2026 22:45:00 +0000

Type Values Removed Values Added
First Time appeared Labring
Labring fastgpt
Vendors & Products Labring
Labring fastgpt

Tue, 07 Jul 2026 21:45:00 +0000

Type Values Removed Values Added
Description FastGPT is an open source AI knowledge base platform. Prior to v4.15.0-beta5, two FastGPT file handlers authorize an unrelated resource and then sign or read an S3 object using a key taken directly from the request, without checking that the key belongs to the caller's team. Because S3 object keys are global within the bucket and carry the tenant id only as a path segment, an attacker can supply another team's key and obtain its file contents through the chat-file presign endpoint or dataset preview endpoint. This issue is fixed in version v4.15.0-beta5.
Title FastGPT: S3 presign/read handlers do not bind the object key to the caller's team (cross-team file disclosure)
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 8.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-09T14:42:06.607Z

Reserved: 2026-06-16T21:48:43.125Z

Link: CVE-2026-55418

cve-icon Vulnrichment

Updated: 2026-07-09T14:38:05.887Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-25T21:00:14Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key