CVE-2026-61684
Auth bypass in FastGPT invoke endpoints lets attackers read user PII and upload files.
Is CVE-2026-61684 being exploited?
Not confirmed. CVE-2026-61684 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-61684?
CVE-2026-61684 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-61684?
Yes. A fix has been recorded for CVE-2026-61684. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-61684 affect?
CVE-2026-61684 affects FastGPT 4.15.0-beta4 (default deployment templates), Any FastGPT deployment using default/unchanged INVOKE_TOKEN_SECRET. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-61684?
Upgrade to 4.15.0-beta5 and set a strong INVOKE_TOKEN_SECRET immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can self-sign HS256 JWT (default secret) to read cross-tenant user PII and write arbitrary chat files.
Immediate action required
- affected= 4.15.0-beta4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.