What’s Vulnerable › Vulnerabilities
CVE-2026-77519: MaxKB: Expired application API keys remain usable on `/chat/api/mcp`
- Severity: medium (CVSS 5.4 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-09-21 · updated 2026-09-24
- Weakness: CWE-613
Description
MaxKB is an open-source AI assistant for enterprise. In 2.10.2-lts and earlier, the /chat/api/mcp authentication path looks up an ApplicationApiKey using only its secret and active status, without enforcing the is_permanent and expire_time checks used by the standard chat API. A previously valid, non-permanent application key that remains active after expiration can initialize the MCP endpoint, list the published application's tool metadata, invoke tools/call, and create durable application_chat and application_chat_record state even though /chat/api/open rejects the same key. No fixed version is available as of this review.
Affected products
- 1Panel-dev MaxKB: through 2.10.2-lts
References
- https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-r6g6-69fh-c39q
- https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-r6g6-69fh-c39q
Get alerted when CVE-2026-77519 or the next vulnerability affects your stack