Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-m5qg-rvjq-727p | NocoDB: OAuth Token Scope Not Enforced at ACL Layer Allows Scope Escalation |
Wed, 24 Jun 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 24 Jun 2026 01:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nocodb
Nocodb nocodb |
|
| Vendors & Products |
Nocodb
Nocodb nocodb |
Tue, 23 Jun 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | NocoDB: OAuth Token Scope Not Enforced at ACL Layer Allows Scope Escalation | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-06-24T13:17:16.868Z
Reserved: 2026-05-14T20:42:31.369Z
Link: CVE-2026-46549
Updated: 2026-06-24T13:17:07.704Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-06-24T09:30:06Z
Github GHSA