Skip to main content
VulnerabilityPublished Updated

CVE-2026-55418: labring FastGPT · Insecure Direct Object Reference

Affects labring FastGPTSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 4.15.0-beta5 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.15.0-beta5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade labring FastGPT to 4.15.0-beta5.

Affected software

ProductAffectedFixed in
labringFastGPTAffected
  • <4.15.0-beta5
Fixed in
  • 4.15.0-beta5
GitHublabring/FastGPTpkg:github/labring/FastGPTOther threatsAffected
  • =4.15.0-beta5
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…