NocoDB Missing Ownership Validation in MCP Token Operations
GHSA-p9x3-w98f-7j3q · CVE-2026-28361
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
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 fk_user_id. 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).
References
- WEB https://github.com/nocodb/nocodb/security/advisories/GHSA-p9x3-w98f-7j3q
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-28361
- WEB https://github.com/nocodb/nocodb/commit/4e736ee40951c7b4f9760f372780e0712c44b9dd
- PACKAGE https://github.com/nocodb/nocodb
- WEB https://github.com/nocodb/nocodb/releases/tag/0.301.3
Ready to move
Start Securing
Free, no credit card | First findings in minutes