vulnerability / NVI-00016135 / Revision 1
NocoDB: Hidden LTAR Column Exposure in Public Shared-View Relation Endpoints
GitHub lists this reviewed advisory for nocodb. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
nocodb
source listed<= 2026.05.0
### Summary 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. ### Details `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. All three handlers now also fetch the shared view's column entries and reject the request unless the matching entry has `show=true`. The four public relation routes covered by the fix are: - `GET /api/v2/public/shared-view/:uuid/rows/:rowId/mm/:columnId` (many-to-many) - `GET /api/v2/public/shared-view/:uuid/rows/:rowId/hm/:columnId` (has-many) - `GET /api/v2/public/shared-view/:uuid/rows/:rowId/{ln,om}/:columnId` (links / one-to-many — both share the many-to-many handler) - `GET /api/v2/public/shared-view/:uuid/nested/:columnId` (form/gallery picker) ### Impact Anyone holding a share UUID could enumerate the full set of linked records for any hidden LTAR column on the view's table by calling the relat
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-9wgh-m22w-9xj8 ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.