dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-47378

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.04.1, Public shared-view endpoints exposed values from columns that the view owner had hidden, via three independent paths: groupBy returned raw values for any column named in the request, filter and sort arrays operated on hidden columns enabling boolean-blind extraction, and the related-data list accepted arbitrary link-column IDs from other tables in the same base. This vulnerability is fixed in 2026.04.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 prior to 2026.04.1 had an information disclosure vulnerability in public shared-view endpoints where hidden column values could be extracted through three independent vectors: groupBy requests returned raw values for any specified column regardless of visibility, filter/sort operations could be performed on hidden columns enabling extraction without boolean feedback, and the related-data list accepted arbitrary link-column IDs from other tables in the same base.

MitigationUpgrade to NocoDB version 2026.04.1 or later which properly enforces hidden column restrictions across all shared-view endpoints.

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. Check installed NocoDB version
    Access the NocoDB administration panel or check the version via API endpoint /api/v1/version or inspect the package.json file in the installation directory. Compare the version number to 2026.04.1.
    Affected if The installed version is earlier than 2026.04.1 (e.g., 2026.03.x, 2026.02.x, or earlier)
  2. Verify public shared-view feature is enabled
    Check the NocoDB system settings or inspect the UI for any shared views that have been published as public (no authentication required). Look for shared view configurations in the Views section of tables.
    Affected if Public shared views exist and are accessible without authentication
  3. Identify hidden columns in shared views
    Review all published shared views and identify which columns have been marked as hidden (typically via column settings in the table designer). Document the names and IDs of hidden columns.
    Affected if Hidden columns exist in any publicly shared view
  4. Test groupBy vector for hidden column exposure
    Create a test API request to a public shared-view endpoint using the groupBy parameter with a hidden column name. For example: GET /api/v1/tables/{tableId}/views/{viewId}?groupBy={hiddenColumnName}. Observe if raw hidden column values are returned in the response.
    Affected if groupBy requests return actual data values from hidden columns rather than restricting access
  5. Test filter/sort vector on hidden columns
    Send a filter or sort request to a public shared-view endpoint targeting a hidden column (e.g., using filter JSON in the request body or query parameters). Verify if the operation executes without returning an access denied error.
    Affected if Filter or sort operations can be performed on hidden columns in shared views without error
  6. Test related-data list vector for cross-table link exposure
    Make a related-data API request to a public shared view using a link-column ID from a different table within the same base. For example: GET /api/v1/tables/{tableId}/views/{viewId}/related/{differentTableLinkColumnId}. Check if data from other tables is returned.
    Affected if The related-data endpoint accepts and returns data for link-column IDs from tables other than the current view's table

The environment is affected if NocoDB version is earlier than 2026.04.1 AND public shared views with hidden columns are in use, particularly if any of the three vectors (groupBy, filter/sort, or related-data) allow access to hidden column values.

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.04.1 or later which properly enforces hidden column restrictions across all shared-view endpoints.

Recommended fix Moderate confidence

2026.04.1

  1. 1. Identify the current NocoDB version in use by checking the deployed application or Docker image tag
  2. 2. Backup all database data and configuration before performing the upgrade
  3. 3. For Docker deployments: Update the image tag to the 2026.04.1 release (e.g., update docker-compose.yml or image: nocodb/nocodb:2026.04.1)
  4. 4. For npm/package installations: Run the appropriate package manager command to upgrade to version 2026.04.1
  5. 5. Restart the NocoDB service to apply the changes
  6. 6. Verify the upgrade was successful by checking the NocoDB version in the UI or via API
  7. 7. Test that public shared-view endpoints now correctly filter hidden columns as expected
Caveat Review release notes for 2026.04.1 to check for any breaking changes or migration requirements

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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