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

No CVSS.

References

Link	Resource
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

Configurations

No configuration.

History

24 Oct 2026, 21:10

Type	Values Removed	Values Added
Summary		(es) FastGPT es una plataforma de aplicación de IA basada en conocimiento. En 4.15.0-beta4, los endpoints de invocación de llamadas inversas del plugin de FastGPT bajo /api/invoke/* se autentican solo verificando un JWT firmado con INVOKE_TOKEN_SECRET, que por defecto es la cadena constante ’token’ y no se configuró en las plantillas de despliegue oficiales. Un atacante no autenticado puede auto-firmar un JWT HS256 y acceder a /api/invoke/userInfo para divulgar PII de usuarios entre inquilinos mediante valores tmbId proporcionados por el atacante, o a /api/invoke/fileUpload para escribir contenido controlado por el atacante en archivos de chat. Este problema está solucionado en la versión 4.15.0-beta5.

Information

Published : 2026-07-15 15:16

Updated : 2026-10-24 21:10

NVD link : CVE-2026-61684

Mitre link : CVE-2026-61684

CVE.ORG link : CVE-2026-61684

JSON object : View

Products Affected

No product.

CWE

CWE-798

Use of Hard-coded Credentials

{"id": "CVE-2026-61684", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-61684", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-07-15T15:07:14.784543Z"}}], "cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.8, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "LOW", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "labring", "product": "FastGPT", "versions": [{"status": "affected", "version": "= 4.15.0-beta4"}]}]}], "published": "2026-07-15T15:16:48.100", "references": [{"url": "https://github.com/labring/FastGPT/commit/f5f1e58b25571b7107ca49d9bf96bb2b0e0a620a", "source": "security-advisories@github.com"}, {"url": "https://github.com/labring/FastGPT/pull/7170", "source": "security-advisories@github.com"}, {"url": "https://github.com/labring/FastGPT/releases/tag/v4.15.0-beta5", "source": "security-advisories@github.com"}, {"url": "https://github.com/labring/FastGPT/security/advisories/GHSA-w732-rq8c-chc8", "source": "security-advisories@github.com"}, {"url": "https://github.com/labring/FastGPT/security/advisories/GHSA-w732-rq8c-chc8", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-798"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "FastGPT es una plataforma de aplicaci\u00f3n de IA basada en conocimiento. En 4.15.0-beta4, los endpoints de invocaci\u00f3n de llamadas inversas del plugin de FastGPT bajo /api/invoke/* se autentican solo verificando un JWT firmado con INVOKE_TOKEN_SECRET, que por defecto es la cadena constante \u2019token\u2019 y no se configur\u00f3 en las plantillas de despliegue oficiales. Un atacante no autenticado puede auto-firmar un JWT HS256 y acceder a /api/invoke/userInfo para divulgar PII de usuarios entre inquilinos mediante valores tmbId proporcionados por el atacante, o a /api/invoke/fileUpload para escribir contenido controlado por el atacante en archivos de chat. Este problema est\u00e1 solucionado en la versi\u00f3n 4.15.0-beta5."}], "lastModified": "2026-10-24T21:10:00.130", "sourceIdentifier": "security-advisories@github.com"}