The vulnerability in NocoDB exists because, before version 2026.04.1, the OAuth token strategy attaches oauth_scope and oauth_granted_resources to the request user, but the ACL middleware never consults these fields. As a result, an OAuth token issued with a restricted scope, such as MCP-only, inherits the full permissions of the underlying user across all routes. Additionally, the granted_resources.base_id restriction is bypassed on org‑level endpoints that do not populate req.context.base_id. This flaw allows an attacker who obtains or generates a scoped token to perform operations beyond the intended scope, effectively escalating privileges. The weakness is an access‑control failure (CWE‑863).

NocoDB (vendor: nocodb, product: nocodb). All releases prior to version 2026.04.1 are affected. Update to 2026.04.1 or later to apply the fix that enforces scope at the ACL layer.

With a CVSS score of 2, the vulnerability is considered low severity, and there is no EPSS data available, suggesting a low likelihood of exploitation. It is not listed in CISA’s KEV catalog. The attack vector is inferred to be through the OAuth token issuance process; an attacker who can control or predict token scopes can bypass ACL checks. No public exploits are reported, but the risk remains for anyone who delegates restricted OAuth scopes to users.