<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T00:14:31.934054+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-329805</id>
    <title>EUVD-2026-329805</title>
    <updated>2026-10-07T00:14:31.936999+00:00</updated>
    <content>EUVD-2026-329805</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-329805"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47279</id>
    <title>fkie_cve-2026-47279</title>
    <updated>2026-10-07T00:14:31.937032+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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's table — including columns the view owner had hidden. 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. This vulnerability is fixed in 2026.05.1.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-47279"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9wgh-m22w-9xj8</id>
    <title>GHSA-9wgh-m22w-9xj8 — NocoDB: Hidden LTAR Column Exposure in Public Shared-View Relation Endpoints</title>
    <updated>2026-10-07T00:14:31.937067+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: nocodb</p>
<p>### 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.</p>
<p>### 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:</p>
<p>- `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)</p>
<p>### 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.</p>
<p>### Credit
This issue was reported by [@leduckhuong](https://github.com/leduckhuong).</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9wgh-m22w-9xj8"/>
  </entry>
</feed>
