CVE-2026-46549: low-severity vulnerability in nocodb
NocoDB: OAuth Token Scope Not Enforced at ACL Layer Allows Scope Escalation
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
8Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 2epss 0.2%
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.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
Affected products
nocodb · nocodbRelated CVEs — nocodb
In the same product, most dangerous first.
CVE-2022-22120MEDIUMNocoDB - Observable Discrepancy in the password-reset featureEPSS 1.4%CVE-2022-22121HIGHNocoDB - CSV Injection in User ManagementEPSS 1.3%CVE-2023-43794MEDIUMSQL Injection in nocodbEPSS 0.9%CVE-2025-27506MEDIUMNocoDB Vulnerable to Reflected Cross-Site Scripting on Reset Password PageEPSS 0.7%CVE-2023-50718MEDIUMNocoDB SQL Injection vulnerabilityEPSS 0.7%CVE-2026-28358LOWNocoDB: User Enumeration via Password Reset EndpointEPSS 0.7%