CVE-2026-77519

published 21 Sep 2026 · updated 24 Sep 2026

MaxKB: Expired application API keys remain usable on `/chat/api/mcp`

5.4MediumCVSS 5.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
1Panel-dev<=2.10.2-lts

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-77519 severity on Zeptric[![CVE-2026-77519](https://zeptric.io/badge/cve/CVE-2026-77519.svg)](https://zeptric.io/cve/CVE-2026-77519)