CVE-2026-130711
NocoDB MCP token identifiers could cross database permission boundaries
nocodb · NocoDB MCP authorization
First documented disclosure · Review checkpoint
Summary
A user’s MCP token identifier could authorize reads against another base.
Severity and exploitation evidence
High · 7.1/10 · CVSS 4.0. Severity source.
Exploitation not established: Malicious exploitation remains unverified in the reviewed sources.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The middleware checked roles against the token’s base while serving data from the base in the request path.
Conditions required
An authenticated user has at least Viewer access to one base and can create an MCP token.
Potential impact
Table metadata and member email addresses from another base can be disclosed.
Affected versions and configurations
Before 2026.09.0.
Fix and mitigation status
2026.09.0.
Practical next steps
Upgrade to 2026.09.0 or later and review cross-base metadata access.
Operating lesson
Use the same resource identity for authorization and data retrieval.
Evidence and limits
Original public disclosure 2026-11-02; CVE publication 2026-11-18. The original advisory demonstrates cross-base reads. Its tested invite path rechecks authorization, so writes are not established.
Sources
- VulnCheck CVE authority record
Primary source ·
- NocoDB MCP authorization original source
Primary source ·
- ENISA EUVD-2026-128783
Primary source ·