GHSA-WVQJ-9WV4-7FF5

Vulnerability from github – Published: 2026-06-05 16:20 – Updated: 2026-06-05 16:20
VLAI
Summary
NocoDB: Path Traversal via SQLite Source Filename
Details

Summary

An authenticated user with base-create permission can attach a SQLite source pointing at an arbitrary file on the NocoDB host, including NocoDB's own internal databases.

Details

The SQLite client and the base/integration create services accepted a caller-supplied filename and passed it to fs.exists and fs.open('w') without restricting the location. A user could point a source at noco.db, at a tenant database under nc_minimal_dbs/, or at any writable path the NocoDB process can reach, and then read or overwrite its contents through the regular table APIs.

Impact

Disclosure and modification of NocoDB internal state, of other tenants' databases, and of any file the NocoDB process can read or write. Authentication and base-create permission are required.

Credit

This issue was reported by @Mouhebbenelwafi.

Severity
5.3 (Medium)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 2026.05.0"
      },
      "package": {
        "ecosystem": "npm",
        "name": "nocodb"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2026.05.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-47385"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-06-05T16:20:20Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "### Summary\nAn authenticated user with base-create permission can attach a SQLite source pointing at\nan arbitrary file on the NocoDB host, including NocoDB\u0027s own internal databases.\n\n### Details\nThe SQLite client and the base/integration create services accepted a caller-supplied\nfilename and passed it to `fs.exists` and `fs.open(\u0027w\u0027)` without restricting the location.\nA user could point a source at `noco.db`, at a tenant database under `nc_minimal_dbs/`,\nor at any writable path the NocoDB process can reach, and then read or overwrite its\ncontents through the regular table APIs.\n\n### Impact\nDisclosure and modification of NocoDB internal state, of other tenants\u0027 databases, and\nof any file the NocoDB process can read or write. Authentication and base-create\npermission are required.\n\n### Credit\nThis issue was reported by [@Mouhebbenelwafi](https://github.com/Mouhebbenelwafi).",
  "id": "GHSA-wvqj-9wv4-7ff5",
  "modified": "2026-06-05T16:20:20Z",
  "published": "2026-06-05T16:20:20Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/nocodb/nocodb/security/advisories/GHSA-wvqj-9wv4-7ff5"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/nocodb/nocodb"
    },
    {
      "type": "WEB",
      "url": "https://github.com/nocodb/nocodb/releases/tag/2026.05.1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "NocoDB: Path Traversal via SQLite Source Filename"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.