The MCP token service did not validate token ownership, allowing a Creator within the same base to read, regenerate, or delete another user's MCP tokens if the token ID was known.
McpTokenService.get(), regenerateToken(), and delete() did not filter by fk_user_id. The analogous ApiTokensService correctly enforced ownership.
Limited — requires Creator role and knowledge of target token ID. Primary risk is denial of service (invalidating tokens) and scoped token disclosure.
This issue was reported by @bugbunny-research (bugbunny.ai).
{
"github_reviewed_at": "2026-03-02T19:53:41Z",
"nvd_published_at": "2026-03-02T17:16:34Z",
"cwe_ids": [
"CWE-639"
],
"severity": "MODERATE",
"github_reviewed": true
}