4.9

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-28361

CVE-2026-28361: NocoDB: Missing Ownership Validation in MCP Token Operations

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-28361

CVE-2026-28361:

4.9

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
nocodb	npm	<= 0.301.2	0.301.3

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability exists in the McpTokenService where the get, regenerateToken, and delete methods failed to validate token ownership. The security advisory explicitly mentioned these functions. By analyzing the patch commit 4e736ee40951c7b4f9760f372780e0712c44b9dd, I confirmed that the fix for this vulnerability was to add an ownership check in these three functions. The patch modifies mcp.service.ts to include a check comparing the fk_user_id on the token with the id of the user making the request (req.user.id). Before the patch, these functions would operate on any token as long as the token ID was valid, allowing a user with a 'Creator' role to read, regenerate, or delete tokens belonging to other users within the same base. The changes in McpGet.operations.ts and McpPost.operations.ts are to pass the request object (req) down to the service layer so the ownership check can be performed.

Vulnerable functions

McpTokenService.get

packages/nocodb/src/services/mcp.service.ts

The `get` function in `McpTokenService` was vulnerable because it retrieved an MCP token by its ID without verifying that the requesting user was the owner of the token. The patch adds a check to compare `token.fk_user_id` with `req.user.id`, thus enforcing ownership.

McpTokenService.regenerateToken

packages/nocodb/src/services/mcp.service.ts

The `regenerateToken` function in `McpTokenService` was vulnerable as it allowed a user to regenerate a token they did not own, simply by knowing the token's ID. The fix introduces an ownership check, ensuring the user ID from the request matches the one associated with the token.

McpTokenService.delete

packages/nocodb/src/services/mcp.service.ts

The `delete` function in `McpTokenService` was vulnerable because it did not validate token ownership before deletion. An attacker could delete another user's MCP token if the token ID was known. The patch adds a check to verify the `fk_user_id` against the requesting user's ID.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.