Skip to main content
VulnerabilityPublished

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

Affects labring FastGPTSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 4.15.0 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.15.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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 20 Nov 2026.

What to do

Upgrade FastGPT and labring/FastGPT to 4.15.0.

Affected software

ProductAffectedFixed in
labringFastGPTAffected
  • <4.15.0
Fixed in
  • 4.15.0
GitHublabring/FastGPTpkg:github/labring/FastGPTOther threatsAffected
  • <4.15.0
Fixed in
  • 4.15.0

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

AI-suggested

Upgrade FastGPT to version 4.15.0 or later, where this authorization bypass vulnerability is fixed. No other mitigation or temporary workaround is indicated. Patch status is not explicitly stated but the fix is included in version 4.15.0.

Description

FastGPT is a knowledge-based AI application platform. Prior to 4.15.0, GET /api/core/ai/record/getRecord authenticates the caller but loads LLM request and response traces only by requestId without team scoping, allowing any authenticated user to read another team's prompts, retrieved RAG chunks, and completions if the requestId is known. This issue is fixed in version 4.15.0.

References

Community reviews

Loading reviews…