<?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, 18 Nov 2026 05:59:18 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-274087</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-274087</link>
      <description>EUVD-2026-274087</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-274087</guid>
    </item>
    <item>
      <title>fkie_cve-2026-28361</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-28361</link>
      <description>&lt;p&gt;NocoDB is software for building databases as spreadsheets. Prior to version 0.301.3, the MCP token service did not validate token ownership, allowing a Creator within the same base to read, regenerate, or delete another user&amp;#39;s MCP tokens if the token ID was known. This issue has been patched in version 0.301.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;NocoDB is software for building databases as spreadsheets. Prior to version 0.301.3, the MCP token service did not validate token ownership, allowing a Creator within the same base to read, regenerate, or delete another user&amp;#39;s MCP tokens if the token ID was known. This issue has been patched in version 0.301.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-28361</guid>
    </item>
    <item>
      <title>GHSA-p9x3-w98f-7j3q — NocoDB Missing Ownership Validation in MCP Token Operations</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p9x3-w98f-7j3q</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nocodb&lt;/p&gt;
&lt;p&gt;### Summary
The MCP token service did not validate token ownership, allowing a Creator within the same base to read, regenerate, or delete another user&amp;#39;s MCP tokens if the token ID was known.&lt;/p&gt;
&lt;p&gt;### Details
`McpTokenService.get()`, `regenerateToken()`, and `delete()` did not filter by `fk_user_id`. The analogous `ApiTokensService` correctly enforced ownership.&lt;/p&gt;
&lt;p&gt;### Impact
Limited — requires Creator role and knowledge of target token ID. Primary risk is denial of service (invalidating tokens) and scoped token disclosure.&lt;/p&gt;
&lt;p&gt;### Credit
This issue was reported by [@bugbunny-research](https://github.com/bugbunny-research) (bugbunny.ai).&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 MCP token service did not validate token ownership, allowing a Creator within the same base to read, regenerate, or delete another user&amp;#39;s MCP tokens if the token ID was known.&lt;/p&gt;
&lt;p&gt;### Details
`McpTokenService.get()`, `regenerateToken()`, and `delete()` did not filter by `fk_user_id`. The analogous `ApiTokensService` correctly enforced ownership.&lt;/p&gt;
&lt;p&gt;### Impact
Limited — requires Creator role and knowledge of target token ID. Primary risk is denial of service (invalidating tokens) and scoped token disclosure.&lt;/p&gt;
&lt;p&gt;### Credit
This issue was reported by [@bugbunny-research](https://github.com/bugbunny-research) (bugbunny.ai).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p9x3-w98f-7j3q</guid>
    </item>
  </channel>
</rss>
