CVE-2026-46549 NocoDB: OAuth Token Scope Not Enforced at ACL Layer Allows Scope Escalation
Attackers with restricted OAuth tokens can bypass scope restrictions to access full user permissions and modify data across all routes.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-46549?
CVE-2026-46549 is a low-severity missing authorization vulnerability in nocodb, published on 23 Jun 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Official description
NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, the OAuth token strategy attached oauth_scope and oauth_granted_resources to the request user, but the ACL middleware never consulted either. An OAuth token issued with a restricted scope (e.g. MCP-only) therefore inherited the full permissions of the underlying user across all routes; the granted_resources.base_id restriction was bypassed on org-level endpoints that don't populate req.context.base_id. This vulnerability is fixed in 2026.04.1.
Weakness: CWE-863
Which versions are affected by CVE-2026-46549?
2 open source packages ship an affected version, including nocodb.
| Package | Affected | Fixed in |
|---|---|---|
nocodb npm | All versions to 0.301.3 | None |
nocodb npm | All versions to 0.301.3 | None |
How do I fix CVE-2026-46549?
No fix has been published for CVE-2026-46549 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-46549 being exploited?
There is no known exploitation of CVE-2026-46549 in the wild and no public exploit code.
Sources
Also known as GHSA-m5qg-rvjq-727p.