🛡️ CVE-2026-47378 — nocodb
Description
NocoDB: Hidden Column Exposure in Public Shared View Endpoints
Summary
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.
Details
A new sanitizeListArgsForPublicView helper now strips request keys that should
never be caller-controlled (e.g. getHiddenColumn, nested), parses where
clauses against a restricted alias map that only contains visible columns, and
recursively removes filter/sort entries whose fk_column_id is not in the visible
set. validateGroupByColumnNames and validateGroupColumnId reject groupBy
requests whose column_name (CSV-style) or groupColumnId is not in the visible
or group-by column set. relDataList now checks `column.fk_model_id ===
currentModel.id` before resolving the linked table, matching the pre-existing
check on publicMmList and publicHmList.
Impact
Anyone with a shared-view UUID could enumerate hidden-column values directly (via
groupBy), confirm hidden-column values by observing row counts (via filter), or
read records from unrelated tables in the same base (via the related-data list).
No authentication was required.
Credit
This issue was reported by [@0xBassia](https://github.com/0xBassia).
It was independently reported by [@b-hermes](https://github.com/b-hermes).
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. Rated impact: confidentiality low, integrity none, availability none.
Weakness class
CVE-2026-47378 is classified as CWE-639: Authorization Bypass Through User-Controlled Key. An object is selected by an identifier from the request without checking the caller owns it.
Affected software
CVE-2026-47378 is recorded against 2 packages.
- nocodb (fixed in 2026.04.1)
- unknown
Timeline and source
Published on 5 June 2026 and last revised on 20 July 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
github.com (Web)
nvd.nist.gov (Advisory)
github.com (Package)
github.com (Web)
Details
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
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| nocodb | — | 2026.04.1 |
| unknown | — | — |
References
Similar Threats
- Medium CVE-2026-24766
- Medium CVE-2026-24767
- Medium CVE-2026-24768
- High CVE-2026-24769
- Medium CVE-2025-27506
More CVE 2026 advisories
Browse all of CVE 2026 in the advisory index.
Free Vulnerability Check
Is your site affected by CVE-2026-47378?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2026-47378 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.