<?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 02:31:14 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-327321</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-327321</link>
      <description>EUVD-2026-327321</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-327321</guid>
    </item>
    <item>
      <title>fkie_cve-2026-11624</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-11624</link>
      <description>&lt;p&gt;The Model Context Protocol has a security warning advising servers to validate the &amp;#34;Origin&amp;#34; header on all incoming connections to prevent DNS rebinding attacks. Prior to the v0.25.0 release, users had no way to validate the origin&amp;#39;s host. In v0.25.0, a new &amp;#34;--allowed-hosts&amp;#34; flag was introduced alongside the existing &amp;#34;--allowed-origins&amp;#34; flag, enabling users to specify permitted hosts at server startup. Both flags default to &amp;#34;*&amp;#34;, allowing users to implement strict access controls as needed without breaking existing setups. If either flag is set to &amp;#34;*&amp;#34;, the server will output a startup warning about potential vulnerabilities. Documentation has also been updated to highlight these security considerations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Model Context Protocol has a security warning advising servers to validate the &amp;#34;Origin&amp;#34; header on all incoming connections to prevent DNS rebinding attacks. Prior to the v0.25.0 release, users had no way to validate the origin&amp;#39;s host. In v0.25.0, a new &amp;#34;--allowed-hosts&amp;#34; flag was introduced alongside the existing &amp;#34;--allowed-origins&amp;#34; flag, enabling users to specify permitted hosts at server startup. Both flags default to &amp;#34;*&amp;#34;, allowing users to implement strict access controls as needed without breaking existing setups. If either flag is set to &amp;#34;*&amp;#34;, the server will output a startup warning about potential vulnerabilities. Documentation has also been updated to highlight these security considerations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-11624</guid>
    </item>
    <item>
      <title>GHSA-76g7-m3xw-x9gr — MCP Toolbox for Databases has an Origin Validation Error</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-76g7-m3xw-x9gr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/googleapis/mcp-toolbox&lt;/p&gt;
&lt;p&gt;The Model Context Protocol has a security warning advising servers to validate the &amp;#34;Origin&amp;#34; header on all incoming connections to prevent DNS rebinding attacks. Prior to the v0.25.0 release, users had no way to validate the origin&amp;#39;s host. In v0.25.0, a new &amp;#34;--allowed-hosts&amp;#34; flag was introduced alongside the existing &amp;#34;--allowed-origins&amp;#34; flag, enabling users to specify permitted hosts at server startup. Both flags default to &amp;#34;*&amp;#34;, allowing users to implement strict access controls as needed without breaking existing setups. If either flag is set to &amp;#34;*&amp;#34;, the server will output a startup warning about potential vulnerabilities. Documentation has also been updated to highlight these security considerations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/googleapis/mcp-toolbox&lt;/p&gt;
&lt;p&gt;The Model Context Protocol has a security warning advising servers to validate the &amp;#34;Origin&amp;#34; header on all incoming connections to prevent DNS rebinding attacks. Prior to the v0.25.0 release, users had no way to validate the origin&amp;#39;s host. In v0.25.0, a new &amp;#34;--allowed-hosts&amp;#34; flag was introduced alongside the existing &amp;#34;--allowed-origins&amp;#34; flag, enabling users to specify permitted hosts at server startup. Both flags default to &amp;#34;*&amp;#34;, allowing users to implement strict access controls as needed without breaking existing setups. If either flag is set to &amp;#34;*&amp;#34;, the server will output a startup warning about potential vulnerabilities. Documentation has also been updated to highlight these security considerations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-76g7-m3xw-x9gr</guid>
    </item>
  </channel>
</rss>
