dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-47385

MEDIUM · 5.3 CVSS v4.0 Published 2026-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, 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. 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.This vulnerability is fixed in 2026.05.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

NocoDB versions prior to 2026.05.1 contain a path traversal vulnerability in the SQLite source attachment feature. An authenticated user with base-create permissions can specify an arbitrary file path that is passed to fs.exists() and fs.open('w') without validation, enabling read/write access to sensitive host files including NocoDB's internal databases (noco.db, tenant databases in nc_minimal_dbs/).

MitigationUpgrade to NocoDB version 2026.05.1 or later, which implements proper path validation to restrict SQLite source file paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify NocoDB version
    Check the running NocoDB instance version through the UI (Settings > About) or by inspecting the package.json file in the installation directory
    Affected if The installed version is prior to 2026.05.1
  2. Confirm SQLite source feature is in use
    Review NocoDB data sources configuration to determine if any bases are using SQLite as an external source
    Affected if SQLite external sources are configured and connected to the instance
  3. Review base-create permissions
    Examine user roles and permissions within NocoDB to identify users granted base-create access
    Affected if Any user accounts have base-create permission enabled
  4. Inspect file system for unexpected files
    Check the host file system for any unexpected files in sensitive locations such as noco.db or nc_minimal_dbs/ directories, or any new files outside expected application directories
    Affected if Unexpected files exist in sensitive directories or files appear to have been created from within the application
  5. Review application logs for path traversal attempts
    Search NocoDB server logs for patterns involving ../ or absolute file paths in SQLite source operations, particularly around fs.exists() and fs.open() calls
    Affected if Logs contain suspicious path traversal patterns in SQLite-related operations

You are affected if your NocoDB version is prior to 2026.05.1 AND the SQLite source feature is enabled with users having base-create permissions, as this combination allows the path traversal to be exploited.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to NocoDB version 2026.05.1 or later, which implements proper path validation to restrict SQLite source file paths.

Recommended fix High confidence

2026.05.1

  1. Backup your current NocoDB installation and database before upgrading
  2. Identify your current NocoDB version to confirm it is prior to 2026.05.1
  3. Upgrade NocoDB to version 2026.05.1 using your deployment method (Docker, npm, etc.)
  4. After upgrade, verify the installation is running correctly
  5. Test that the path traversal vulnerability is no longer exploitable by confirming SQLite sources are restricted to allowed directories

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47385 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47385 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data