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.
CVE-2026-55418
This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(medium)
- EPSS
- 21.7%
- KEV
- Not listed
Published
July 7, 2026
Last Modified
July 9, 2026
Advisory Details (4)
Auto-updated Jul 7, 2026S3 presign/read handlers do not bind the object key to the caller's team (cross-team file disclosure) · Advisory · labring/FastGPT · GitHub
https://github.com/labring/FastGPT/security/advisories/GHSA-6rxv-p43w-mmx5v4.15.0-beta5
Patch available: labring/FastGPT v4.15.0-beta5 (pre-release)
https://github.com/labring/FastGPT/releases/tag/v4.15.0-beta5fix: bind S3 object keys to authorized resources
Patch available: labring/FastGPT v4.15.0-beta5 (PR #7104 merged 2026-06-12)
https://github.com/labring/FastGPT/pull/7104commit decb6d2fb141 (labring/FastGPT)
Patch available: labring/FastGPT v4.15.0-beta5 (contains commit decb6d2fb141)
https://github.com/labring/FastGPT/commit/decb6d2fb1417fb9e2bca145d2dcc9cbcf06396cWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 02:33 UTCEG score recompute
- 2026-07-12 14:04 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 01:33 UTCEG score recompute
- 2026-07-11 13:04 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 00:33 UTCEG score recompute
- 2026-07-10 12:03 UTCEG score recompute
- 2026-07-09 23:33 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 11:04 UTCEG score recompute
- 2026-07-08 22:35 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 10:07 UTCEG score recompute
- 2026-07-07 21:37 UTCEG score recompute
- 2026-07-07 21:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-55418?
When was CVE-2026-55418 disclosed?
Is CVE-2026-55418 actively exploited?
What is the CVSS score of CVE-2026-55418?
How do I remediate CVE-2026-55418?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55418
Is Your Infrastructure Affected by CVE-2026-55418?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.