CVE-2026-28361

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](https://github.com/bugbunny-research) (bugbunny.ai).

How to fix CVE-2026-28361

To remediate CVE-2026-28361, upgrade the affected package to a fixed version below.

• —upgrade to 0.301.3 or later

Is CVE-2026-28361 being exploited?

Low — EPSS is 0.1%, meaning exploitation activity has not been observed at scale.

Affected packages (1)

• from 0, < 0.301.3

CVSS scores

References (4)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-28361
• PATCHgithub.com/nocodb/nocodb
• WEBgithub.com/nocodb/nocodb/releases/tag/0.301.3
• WEBgithub.com/nocodb/nocodb/security/advisories/GHSA-p9x3-w98f-7j3q