dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-47279

MEDIUM · 6.9 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 →
78/100
Remediation priority · High
Remotely reachable No privileges 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, the public shared-view relation endpoints accepted a caller-supplied column ID without verifying that the column was visible in the shared view, so anyone holding a share UUID could read links from any LTAR column on the view's table — including columns the view owner had hidden. publicMmList, publicHmList, and relDataList already ensured that the requested column belonged to the view's model, but did not check the view-column entry's show flag. 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

In NocoDB prior to 2026.05.1, the public shared-view relation endpoints (publicMmList, publicHmList, relDataList) accepted caller-supplied column IDs without verifying the view-column entry's show flag. This allowed anyone with a share UUID to read data from hidden LTAR (Link to Another Record) columns in the table, exposing links the view owner had intended to hide.

MitigationUpgrade to NocoDB version 2026.05.1 or later. As a workaround, avoid using shared views until the upgrade is applied, as the vulnerability allows unauthorized data disclosure of hidden columns.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/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
    Query the NocoDB instance for its version number via API (e.g., /api/v1/db/meta/version) or check the running container/image tag
    Affected if the installed version is earlier than 2026.05.1
  2. Confirm shared views are in use
    Check if any shared view UUIDs exist in the database (nc_store table with key pattern like 'share%') or if shared links have been generated for views
    Affected if shared views are active and exposed via UUID URLs
  3. Check for hidden LTAR columns in shared views
    Query the view-column mappings (nc_evolutions or equivalent table storing view-column configurations) for entries where show=false and column type includes 'ltar' or 'linkToAnotherRecord'
    Affected if hidden LTAR columns exist in any shared view configuration
  4. Test vulnerable endpoints for unauthorized data access
    Using a known shared view UUID, call the publicMmList, publicHmList, or relDataList endpoints with column IDs corresponding to hidden LTAR columns and verify if data is returned
    Affected if the endpoints return LTAR link data despite the show flag being false for those columns

A NocoDB instance is affected if it runs a version prior to 2026.05.1 AND has shared views enabled with hidden LTAR columns, as the public relation endpoints will expose those hidden columns to anyone with the share UUID.

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. As a workaround, avoid using shared views until the upgrade is applied, as the vulnerability allows unauthorized data disclosure of hidden columns.

Recommended fix Moderate confidence

NocoDB version 2026.05.1

  1. 1. Identify the current NocoDB version running in your environment
  2. 2. Upgrade NocoDB to version 2026.05.1 or later
  3. 3. Verify the upgrade was successful by checking the NocoDB version
  4. 4. Test that shared view column visibility controls now work correctly by creating a shared view with hidden LTAR columns and confirming they cannot be accessed via the public endpoints
Caveat Review NocoDB release notes for 2026.05.1 to check for any breaking changes between your current version and 2026.05.1

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47279 — 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-47279 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