Vulnerability · Published Sep 21, 2026 · Assigned by GitHub_M

CVE-2026-77519MaxKB: Expired application API keys remain usable on `/chat/api/mcp`

Medium 5.4

In plain English

A medium-severity security flaw in MaxKB from 1Panel-dev. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 15% of all known vulnerabilities).

Severity (CVSS 3.1)5.4Medium

Exploit odds (30 days)0.2%top 84.8% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

Official 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 (as reported)

Vendor	Product	Versions
1Panel-dev	MaxKB	<= 2.10.2-lts

Weakness: CWE-613 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

References

https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-r6g6-69fh-c39q x_refsource_CONFIRM