<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 00:09:40 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-329805</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329805</link>
      <description>EUVD-2026-329805</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329805</guid>
    </item>
    <item>
      <title>fkie_cve-2026-47279</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47279</link>
      <description>&lt;p&gt;NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, 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&amp;#39;s table — including columns the view owner had hidden. publicMmList, publicHmList, and relDataList already ensured that the requested column belonged to the view&amp;#39;s model, but did not check the view-column entry&amp;#39;s show flag. This vulnerability is fixed in 2026.05.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, 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&amp;#39;s table — including columns the view owner had hidden. publicMmList, publicHmList, and relDataList already ensured that the requested column belonged to the view&amp;#39;s model, but did not check the view-column entry&amp;#39;s show flag. This vulnerability is fixed in 2026.05.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-47279</guid>
    </item>
    <item>
      <title>GHSA-9wgh-m22w-9xj8 — NocoDB: Hidden LTAR Column Exposure in Public Shared-View Relation Endpoints</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9wgh-m22w-9xj8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nocodb&lt;/p&gt;
&lt;p&gt;### 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&amp;#39;s table — including columns the view owner had hidden.&lt;/p&gt;
&lt;p&gt;### Details
`publicMmList`, `publicHmList`, and `relDataList` already ensured that the
requested column belonged to the view&amp;#39;s model, but did not check the
view-column entry&amp;#39;s `show` flag. All three handlers now also fetch the
shared view&amp;#39;s column entries and reject the request unless the matching
entry has `show=true`. The four public relation routes covered by the fix
are:&lt;/p&gt;
&lt;p&gt;- `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)&lt;/p&gt;
&lt;p&gt;### Impact
Anyone holding a share UUID could enumerate the full set of linked records
for any hidden LTAR column on the view&amp;#39;s table by calling the relation
endpoint directly, even when the same column was correctly omitted from the
public `/rows` response.&lt;/p&gt;
&lt;p&gt;### Credit
This issue was reported by [@leduckhuong](https://github.com/leduckhuong).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nocodb&lt;/p&gt;
&lt;p&gt;### 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&amp;#39;s table — including columns the view owner had hidden.&lt;/p&gt;
&lt;p&gt;### Details
`publicMmList`, `publicHmList`, and `relDataList` already ensured that the
requested column belonged to the view&amp;#39;s model, but did not check the
view-column entry&amp;#39;s `show` flag. All three handlers now also fetch the
shared view&amp;#39;s column entries and reject the request unless the matching
entry has `show=true`. The four public relation routes covered by the fix
are:&lt;/p&gt;
&lt;p&gt;- `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)&lt;/p&gt;
&lt;p&gt;### Impact
Anyone holding a share UUID could enumerate the full set of linked records
for any hidden LTAR column on the view&amp;#39;s table by calling the relation
endpoint directly, even when the same column was correctly omitted from the
public `/rows` response.&lt;/p&gt;
&lt;p&gt;### Credit
This issue was reported by [@leduckhuong](https://github.com/leduckhuong).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9wgh-m22w-9xj8</guid>
    </item>
  </channel>
</rss>
