Vulnerability  ·  2026-11-19

NocoDB cross-base authorization bypass via MCP token identifier (CVE-2026-130711)

VulnerabilityMedium impactGlobalCVE-2026-130711
NocoDB before 2026.09.0 has an authorization-bypass defect in extract-ids.middleware.ts. The middleware resolves two independent anchors per request: a data anchor (which base's data is served) and a role anchor (which base the caller's roles resolve against). On base-scoped routes it read an MCP token id from the query string and used it to re-point the role anchor, resolving the token under a full-bypass scope so any token on the instance resolved — while the data anchor stayed on the base named in the path. There is no legitimate route pairing an MCP token id with a base id, so this only lets a caller pass the permission check with roles they hold on their own base.
NocoDB is a popular open-source no-code database. An authenticated user with only Viewer on one base can mint an MCP token on that base and pass its id to re-point role resolution, then read another base's metadata — including table lists and the base user roster with member email addresses — despite having no role on the target base. For agentic/data platforms this is a cross-tenant authorization bypass on a data surface agents commonly read from.
Authenticated user with Viewer on one base mints an MCP token and supplies its id in the query string to a base-scoped route, causing roles to resolve against their own base while the handler serves another base, exposing that base's metadata and user roster.
NocoDB before 2026.09.0 (Community and Enterprise middlewares)
Upgrade NocoDB to 2026.09.0 or later, which removes the query-string MCP token-id fallback and re-resolves roles against the data base.
NocoDB security advisory GHSA-4m8g-w724-935gNVD detail — CVE-2026-130711
See this in the live feed Explore related AI security and governance findings — updated every morning.
Open the feed →