### 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).
### 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).
Update nocodb to 2026.04.1 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanNocoDB: Hidden Column Exposure in Public Shared View Endpoints affects nocodb (npm). Severity is medium. ### 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).
AI coding agents often install or upgrade packages automatically in npm. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| nocodbnpm | <2026.04.1 | 2026.04.1 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate nocodb to 2026.04.1 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanNocoDB: Hidden Column Exposure in Public Shared View Endpoints affects nocodb (npm). Severity is medium. ### 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).
AI coding agents often install or upgrade packages automatically in npm. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| nocodbnpm | <2026.04.1 | 2026.04.1 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard