CVE-2026-47388: NocoDB Missing Ownership Check Vulnerability

LOW
Advisory Identifier: GHSA-xxpj-q764-9r6q
Share
CWE-639
Published
Advisory Summary

CVE-2026-47388 is a LOW missing ownership check vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting NocoDB libraries in the npm ecosystem. The issue involves missing ownership check in mcp attachment read. Remediation is available by upgrading affected packages to version 2026.05.1.

CVE-2026-47388 at a Glance

CVE Identifier CVE-2026-47388
GHSA Identifier GHSA-xxpj-q764-9r6q
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product NocoDB
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-47388

To remediate this vulnerability, upgrade all affected NocoDB dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nocodb fixed: 2026.05.1 
npm install nocodb@2026.05.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls nocodb

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-47388, inspect your project dependencies using npm:

npm ls nocodb

Analyze the terminal output to locate any version of NocoDB in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.05.1), your application is affected.

Note: The npm ls nocodb command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In NocoDB, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A low-privilege MCP token holder with knowledge of an attachment path could read any file in shared storage, including attachments belonging to other bases and workspaces, because the MCP `readAttachment` tool did not verify the file's ownership. ### Details The MCP `readAttachment` tool accepts caller-supplied `path`/`url` values and streams the file via the storage adapter. The handler now looks up the path in `nc_file_references` and requires a non-deleted row whose `base_id` matches the caller's MCP context before streaming; otherwise it returns `Attachment is not accessible from this MCP context`. The lookup tolerates both `download/uploads/...` and `uploads/...` styles. ### Impact Arbitrary read against shared storage scoped to attachments the caller's MCP context should not see. Exploitation requires an MCP token and a known attachment path. ### Credit This issue was reported by [@helwor-01](https://github.com/helwor-01).

CVE-2026-47388 Affected NocoDB Versions

1 component(s)
Fixed Versions:
2026.05.1
Product / Package Ecosystem Affected Versions Fixed Version
nocodb
npm/nocodb
npm
< 2026.05.1
2026.05.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/nocodb/nocodb/security/advisories/GHSA-xxpj-q764-9r6q
NVD — CVE-2026-47388 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-47388
NocoDB Source Repository REPOSITORY
https://github.com/nocodb/nocodb
NocoDB Release RELEASE
https://github.com/nocodb/nocodb/releases/tag/2026.05.1

Frequently Asked Questions

What is CVE-2026-47388?
CVE-2026-47388 is a security vulnerability in NocoDB involving Missing Ownership Check in MCP Attachment Read under CWE-639: Authorization Bypass Through User-Controlled Key.
Which NocoDB versions are affected?
Affected versions include releases prior to 2026.05.1 across affected packages: nocodb.
What version fixes CVE-2026-47388?
Upgrading to 2026.05.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nocodb affected?
Yes, nocodb is affected in releases prior to 2026.05.1. Upgrade your dependency to 2026.05.1 or later.
What CWE is associated with CVE-2026-47388?
CVE-2026-47388 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check npm dependencies for CVE-2026-47388?
Run the dependency tree command: 'npm ls nocodb'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xxpj-q764-9r6q",
  "modified" : "2026-07-20T21:19:03Z",
  "published" : "2026-06-05T16:22:28Z",
  "aliases" : [ "CVE-2026-47388" ],
  "summary" : "NocoDB: Missing Ownership Check in MCP Attachment Read",
  "details" : "### Summary\nA low-privilege MCP token holder with knowledge of an attachment path could read any\nfile in shared storage, including attachments belonging to other bases and workspaces,\nbecause the MCP `readAttachment` tool did not verify the file's ownership.\n\n### Details\nThe MCP `readAttachment` tool accepts caller-supplied `path`/`url` values and streams\nthe file via the storage adapter. The handler now looks up the path in\n`nc_file_references` and requires a non-deleted row whose `base_id` matches the\ncaller's MCP context before streaming; otherwise it returns\n`Attachment is not accessible from this MCP context`. The lookup tolerates both\n`download/uploads/...` and `uploads/...` styles.\n\n### Impact\nArbitrary read against shared storage scoped to attachments the caller's MCP context\nshould not see. Exploitation requires an MCP token and a known attachment path.\n\n### Credit\nThis issue was reported by [@helwor-01](https://github.com/helwor-01).",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "nocodb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.05.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2026.05.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/nocodb/nocodb/security/advisories/GHSA-xxpj-q764-9r6q"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-47388"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/nocodb/nocodb"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/nocodb/nocodb/releases/tag/2026.05.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-05T16:22:28Z",
    "nvd_published_at" : "2026-06-23T21:17:00Z"
  }
}