CVE-2026-54601

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.3
EG Score
6.3(medium)
EPSS
15.8%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 8, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_release, github, github_commit.
github Patch Available🟡 PoC Available

FastGPT: reTrainingCollection allows server-owned datasetId override causing cross-tenant authorization confusion · Advisory · labring/FastGPT · GitHub

https://github.com/labring/FastGPT/security/advisories/GHSA-qxcq-48gr-93pj
github_release Patch Available

v4.15.0-beta4

Patch available: labring/FastGPT v4.15.0-beta4 (pre-release)

https://github.com/labring/FastGPT/releases/tag/v4.15.0-beta4
github_pr Patch Available

fix: bind dataset training operations to collection ownership

Patch available: labring/FastGPT v4.15.0-beta4 (PR #7071 merged 2026-06-07)

https://github.com/labring/FastGPT/pull/7071
github_commit Patch Available

commit 54a53e7d4399 (labring/FastGPT)

Patch available: labring/FastGPT v4.15.0-beta4 (contains commit 54a53e7d4399)

https://github.com/labring/FastGPT/commit/54a53e7d4399f1dfa2913394442c3cf6de672fb3

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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.

  1. 2026-07-11 14:17 UTCEG score recompute
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-10 16:08 UTCEG score recompute
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-09 17:58 UTCEG score recompute
  8. 2026-07-08 19:50 UTCEG score recompute
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-07 21:37 UTCEG score recompute
  12. 2026-07-07 21:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54601?
CVE-2026-54601 is a medium vulnerability published on July 7, 2026. 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…
When was CVE-2026-54601 disclosed?
CVE-2026-54601 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54601 actively exploited?
CVE-2026-54601 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54601?
CVE-2026-54601 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-54601?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54601, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54601

Explore →

Is Your Infrastructure Affected by CVE-2026-54601?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs