CVE-2026-61684

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.

CVSS 4.0

8.8CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

EPSS

0.4% chance of exploitation in the next 30 days; higher than 32% of CVEs (scores of 2026-10-25)

CWE

CWE-798

Published

2026-07-15

Modified

2026-10-24

Record from

the NVD, synced 2026-10-25

References

• https://github.com/labring/FastGPT/commit/f5f1e58b25571b7107ca49d9bf96bb2b0e0a620a
• 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

Check your stackJSON