NocoDB: OAuth Token Scope Not Enforced at ACL Layer Allows Scope Escalation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

2.0 · CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-46549: 0.24% estimated exploitation activity in the next 30 days; percentile 15.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The OAuth token strategy attached oauthscope and oauthgrantedresources 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 grantedresources.baseid restriction was bypassed on org-level endpoints that don't populate req.context.baseid. Details In packages/nocodb/src/strategies/oauth-token.strategy.ts, the strategy set isoauthtoken, oauthclientid, oauthgrantedresources, and oauthscope on the user object, then mapped through to the user's existing roles / baseroles. The ACL middleware in extract-ids.middleware.ts honoured isapitoken via blockApiTokenAccess but had no equivalent gate for isoauthtoken or scope-string enforcement. The base/workspace restriction logic short-circuited when req.context.baseid was unset (org-level routes), so an OAuth token scoped to one base could still call org-level endpoints as the…

Published by the source

21 May 2026, 20:34 UTC

Last modified by the source

20 Jul 2026, 21:30 UTC

Source last checked

26 Oct 2026, 12:57 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-m5qg-rvjq-727p

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-m5qg-rvjq-727p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46549

Advisory: NocoDB: OAuth Token Scope Not Enforced at ACL Layer Allows Scope Escalation
IDs: CVE-2026-46549, GHSA-m5qg-rvjq-727p
Record: https://patchnext.com/advisories/cve-2026-46549 (revision 2, source checked 26 Oct 2026, 12:57 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nocodb: affected <= 0.301.3

## Suggested inspection (read-only)
- `npm ls nocodb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nocodb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-m5qg-rvjq-727p (OSV record GHSA-m5qg-rvjq-727p lists affected ranges: npm nocodb >=0 <=0.301.3)
- Verified: https://github.com/advisories/GHSA-m5qg-rvjq-727p (GitHub-reviewed advisory GHSA-m5qg-rvjq-727p lists affected ranges: npm nocodb >=0 <=0.301.3)

Commands are suggestions: review each one before running it.