Technical impact
The vulnerability resides in the extract‑ids.middleware.ts file of NocoDB versions prior to 2026.09.0. An authenticated user can supply an MCP token identifier in the query string, leading the server to resolve roles against another base. This permits a Viewer‑level user of one base to obtain a token, use its id in a request, and read metadata—including table lists and member e‑mail addresses—of a different base. The flaw is an access control weakness identified as CWE-639, allowing an attacker to bypass authorization checks.
Affected Systems
NocoDB deployments running any version earlier than 2026.09.0 are affected. Affected vendors/products include NocoDB by the NocoDB organization. No specific version constraints beyond the major release; any release before 2026.09.0 is impacted.
Risk and Exploitability
The CVSS base score of 7.1 classifies the issue as high severity. Because the vulnerability requires an authenticated user, an attacker needs at least Viewer access to a base and the ability to request token generation. Once possession of an MCP token id is obtained, the attacker can use a crafted query to access another base's protected metadata. EPSS data is unavailable, but the lack of KEV listing suggests this flaw has not yet been widely exploited. Nevertheless, the potential for cross‑base data exposure warrants immediate attention, and the risk of exploitation is considered moderate to high in environments where user tokens are not strictly monitored.