CVE-2026-28361: NocoDB: Missing Ownership Validation in MCP Token Operations
Summary 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.
Details McpTokenService.get(), regenerateToken(), and delete() did not filter by fkuserid. The analogous ApiTokensService correctly enforced ownership.
Impact Limited — requires Creator role and knowledge of target token ID. Primary risk is denial of service (invalidating tokens) and scoped token disclosure.
Credit This issue was reported by @bugbunny-research (bugbunny.ai).
Other sources
NocoDB is software for building databases as spreadsheets. Prior to version 0.301.3, 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. This issue has been patched in version 0.301.3.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-28361?
CVE-2026-28361 is considered a high-severity vulnerability due to its potential for unauthorized access to user tokens.
How do I fix CVE-2026-28361?
To fix CVE-2026-28361, upgrade NocoDB to version 0.301.3 or later, which includes the necessary ownership validation.
Who is affected by CVE-2026-28361?
CVE-2026-28361 affects all versions of NocoDB up to 0.301.2.
What type of attacks does CVE-2026-28361 enable?
CVE-2026-28361 allows unauthorized users to read, regenerate, or delete another user's MCP tokens if they know the token ID.
What components are involved in CVE-2026-28361?
CVE-2026-28361 specifically involves the McpTokenService operations that lack proper ownership validation.