Skip to main content
VulnerabilityPublished

CVE-2026-54601: labring FastGPT · Mass Assignment

Affects labring FastGPTSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.15.0-beta4 when convenient.

Data as of 19 Nov 2026, 20:25 UTC

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

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 19 Nov 2026.

What to do

Upgrade labring FastGPT to 4.15.0-beta4.

Affected software

ProductAffectedFixed in
labringFastGPTAffected
  • >=4.14.17 <4.15.0-beta4
Fixed in
  • 4.15.0-beta4

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

AI-suggested

The vulnerability is fixed in FastGPT version 4.15.0-beta4. Users should upgrade to version 4.15.0-beta4 or later to remediate this issue. No official remediation level or patch link is provided, so verify with the vendor for the latest updates and apply the official fix accordingly.

Description

FastGPT is an open source AI knowledge base platform. From 4.14.17 to before 4.15.0-beta4, FastGPT allows an authenticated tenant user to call POST /api/core/dataset/collection/create/reTrainingCollection in a way that persists a server-owned datasetId value from another tenant. This creates mixed dataset objects and downstream dataset, collection, and training endpoints then make authorization decisions from inconsistent ownership anchors, allowing cross-tenant read, update, and delete access when mixed object ids are known. This issue is fixed in version 4.15.0-beta4.

References

Community reviews

Loading reviews…