CVE-2026-77519 MaxKB: Expired application API keys remain usable on `/chat/api/mcp`
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- Proof of concept public · automatable: no · technical impact: partial
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.
Upgrade path
1 package: 0 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| 1Panel-dev MaxKB | = <= 2.10.2-lts | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| 1Panel-dev MaxKB | = <= 2.10.2-lts | No fix listed |
References
- https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-r6g6-69fh-c39q exploit
- ENISA EUVD EUVD-2026-84196 third-party-advisory