Answer in brief
CVE-2026-28361 records a Medium severity (CVSS 0.0) vulnerability in NocoDB Missing Ownership Validation in MCP Token Operations. The current sources do not mark it as known exploited. The current feed maps nocodb (npm), nocodb (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 0.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps nocodb (npm), nocodb (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| nocodbnpm | <=0.301.2 | 0.301.3 |
| nocodbnpm | >=0 <0.301.3 | 0.301.3 |
Published upstream
Mar 2, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
### 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).
Quoted source text, attributed separately from HOL analysis.