{"id":"CVE-2026-77519","published":"2026-09-21T21:17:10.633","lastModified":"2026-09-21T21:17:10.750","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.","cvssScore":5.4,"cvssSeverity":"MEDIUM","cvssVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","cwes":["CWE-613"],"vendors":[],"products":[],"references":[{"url":"https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-r6g6-69fh-c39q","tags":[]}],"exploitRefs":[{"url":"https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-r6g6-69fh-c39q","tags":[]}],"hasPoc":true,"ai":{"summary":"The flaw allows an attacker to exploit a previously valid, non-permanent application key that remains active after expiration to access and manipulate MCP endpoint functionalities.","exploitability":"Exploitation requires knowledge of the expired but still active ApplicationApiKey secret; it is moderately difficult due to the need for API key manipulation.","blast_radius":"If exploited, this could lead to unauthorized access, data manipulation, and potential misuse of enterprise tools through the MCP endpoint.","remediation":"Discontinue use of non-permanent application keys or implement stricter validation checks on key expiration and permanent status before allowing access.","tags":["api-bypass","auth-exploit","data-misuse","security-flaw"],"model":"qwen2.5:7b-instruct","analyzedAt":"2026-09-22T06:26:41.225Z"}}