Vulnerability Description
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.
Related Weaknesses (CWE)
References
- https://github.com/labring/FastGPT/commit/f5f1e58b25571b7107ca49d9bf96bb2b0e0a62
- https://github.com/labring/FastGPT/pull/7170
- https://github.com/labring/FastGPT/releases/tag/v4.15.0-beta5
- https://github.com/labring/FastGPT/security/advisories/GHSA-w732-rq8c-chc8
- https://github.com/labring/FastGPT/security/advisories/GHSA-w732-rq8c-chc8
FAQ
What is CVE-2026-61684?
CVE-2026-61684 is a documented vulnerability. 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_SE...
How severe is CVE-2026-61684?
CVSS scoring is not yet available for CVE-2026-61684. Check NVD for updates.
Is there a patch for CVE-2026-61684?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.