CVE-2026-46549

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

LOW
2
CVSS Score
Published: June 23, 2026 at 08:40 PM UTC
Updated: June 27, 2026 at 11:42 AM UTC
1 product affected across 1 vendorNocodb

Using nocodb by nocodb?

Get instant alerts when new vulnerabilities affect nocodb - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW2
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2026.04.1
Affected range stops below 2026.04.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

2LOWGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
HIGH
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-863

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card