Medium severity · published Sep 21, 2026
CVE-2026-77519
MaxKB: Expired application API keys remain usable on `/chat/api/mcp`
5.4
CVSS
0.2%
EPSS
No
On KEV
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
Low
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 15% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
MA
MaxKB · 1Panel-dev
<= 2.10.2-lts · source: vendor
Affected product
MA
MaxKB
1Panel-dev
More from MaxKB
10.0
CVE-2026-77521
MaxKB: Prompt-injectable agent can lead to command execution
10.0
CVE-2025-66419
MaxKB vulnerable to privilege escalation through sandbox bypass
9.8
CVE-2025-53928
MaxKB has RCE in MCP call
9.1
CVE-2026-79916
MaxKB AWS Bedrock model credential injection leads to remote code execution
8.8
CVE-2026-54149
MaxKB MCP tool import validation bypass allows post-authentication remote code execution