FastGPT is a knowledge-based AI application platform. In 4.15.0-beta4, FastGPT plugin invoke reverse-call endpoints under /api/invoke/* authenticate only by verifying a JWT signed with INVOKE_TOKEN_SECRET, which defaults to the constant string token and was not set in official deployment templates. An unauthenticated attacker can self-sign an HS256 JWT and reach /api/invoke/userInfo to disclose cross-tenant user PII by attacker-supplied tmbId values, or /api/invoke/fileUpload to write attacker-controlled content into chat files. This issue is fixed in version 4.15.0-beta5.
CVE-2026-61684
HIGHPre-NVD 8.88.8Elevated
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 8.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available
Unauthenticated cross-tenant data access via forgeable plugin-invoke JWT (default INVOKE_TOKEN_SECRET='token') · Advisory · labring/FastGPT · GitHub
https://github.com/labring/FastGPT/security/advisories/GHSA-w732-rq8c-chc8github_release Patch Available
v4.15.0-beta5
Patch available: labring/FastGPT v4.15.0-beta5 (pre-release)
https://github.com/labring/FastGPT/releases/tag/v4.15.0-beta5github_pr Patch Available
fix: require invoke token secret configuration
Patch available: labring/FastGPT v4.15.0-beta5 (PR #7170 merged 2026-06-23)
https://github.com/labring/FastGPT/pull/7170github_commit Patch Available
commit f5f1e58b2557 (labring/FastGPT)
Patch available: labring/FastGPT v4.15.0-beta5 (contains commit f5f1e58b2557)
https://github.com/labring/FastGPT/commit/f5f1e58b25571b7107ca49d9bf96bb2b0e0a620aWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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-16 01:41 UTCEG score recompute
- 2026-07-15 14:51 UTCEG score recompute
- 2026-07-15 14:49 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-61684?
CVE-2026-61684 is a high vulnerability published on July 15, 2026. FastGPT is a knowledge-based AI application platform. In 4.15.0-beta4, FastGPT plugin invoke reverse-call endpoints under /api/invoke/* authenticate only by verifying a JWT signed with INVOKETOKENSECRET, which defaults to the constant string token and was not set in official deployment templates.…
When was CVE-2026-61684 disclosed?
CVE-2026-61684 was first published in the National Vulnerability Database on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-61684?
CVE-2026-61684 has a CVSS v3 base score of 8.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-61684?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61684, 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-61684
Is Your Infrastructure Affected by CVE-2026-61684?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.