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)
Credit
This issue was reported by @leduckhuong.
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 relation
endpoint directly, even when the same column was correctly omitted from the
public /rows response.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-47279? CVE-2026-47279 is a medium-severity security vulnerability in nocodb (npm), affecting versions <= 2026.05.0. It is fixed in 2026.05.1.
- Which versions of nocodb are affected by CVE-2026-47279? nocodb (npm) versions <= 2026.05.0 is affected.
- Is there a fix for CVE-2026-47279? Yes. CVE-2026-47279 is fixed in 2026.05.1. Upgrade to this version or later.
- Is CVE-2026-47279 exploitable, and should I be worried? Whether CVE-2026-47279 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-47279 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-47279? Upgrade
nocodbto 2026.05.1 or later.