CVE-2026-55418: CWE-639: Authorization Bypass Through User-Controlled Key in labring FastGPT
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.
AI Analysis
Technical Summary
FastGPT versions before 4.15.0-beta5 contain an authorization bypass vulnerability (CWE-639) where two file handlers improperly authorize resources but then sign or read S3 objects using user-supplied keys without verifying that the key belongs to the caller's team. Because S3 object keys are global within the bucket and tenant identification is only part of the path, an attacker can supply keys belonging to other teams to access their files through the chat-file presign or dataset preview endpoints. This issue is resolved in version 4.15.0-beta5.
Potential Impact
An attacker without privileges can access files belonging to other teams by supplying their S3 object keys, leading to unauthorized disclosure of sensitive data. The vulnerability affects confidentiality but does not impact integrity or availability. The CVSS 3.1 base score is 8.6 (high severity), reflecting network attack vector, low complexity, no privileges required, no user interaction, and high confidentiality impact with scope change.
Mitigation Recommendations
The vendor has fixed this vulnerability in FastGPT version 4.15.0-beta5. Since this is a cloud service, the vendor manages remediation server-side. Users should verify with the vendor advisory that their service instance is updated to at least version 4.15.0-beta5 to ensure the vulnerability is mitigated.
CVE-2026-55418: CWE-639: Authorization Bypass Through User-Controlled Key in labring FastGPT
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.
CVSS v3.1
Score 8.6high
Affected software
pkg:github/labring/FastGPTRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
FastGPT versions before 4.15.0-beta5 contain an authorization bypass vulnerability (CWE-639) where two file handlers improperly authorize resources but then sign or read S3 objects using user-supplied keys without verifying that the key belongs to the caller's team. Because S3 object keys are global within the bucket and tenant identification is only part of the path, an attacker can supply keys belonging to other teams to access their files through the chat-file presign or dataset preview endpoints. This issue is resolved in version 4.15.0-beta5.
Potential Impact
An attacker without privileges can access files belonging to other teams by supplying their S3 object keys, leading to unauthorized disclosure of sensitive data. The vulnerability affects confidentiality but does not impact integrity or availability. The CVSS 3.1 base score is 8.6 (high severity), reflecting network attack vector, low complexity, no privileges required, no user interaction, and high confidentiality impact with scope change.
Mitigation Recommendations
The vendor has fixed this vulnerability in FastGPT version 4.15.0-beta5. Since this is a cloud service, the vendor manages remediation server-side. Users should verify with the vendor advisory that their service instance is updated to at least version 4.15.0-beta5 to ensure the vulnerability is mitigated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T21:48:43.125Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Is Cloud Service
- true
Threat ID: 6a4d7350c9d9e3dbe3e36b35
Added to database: 07/07/2026, 21:44:48 UTC
Last enriched: 07/15/2026, 11:54:49 UTC
Last updated: 08/20/2026, 10:52:10 UTC
Views: 129
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.