<?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 20:37:32 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-328452</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-328452</link>
      <description>EUVD-2026-328452</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-328452</guid>
    </item>
    <item>
      <title>fkie_cve-2026-11717</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-11717</link>
      <description>&lt;p&gt;An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.&lt;/p&gt;
&lt;p&gt;When verifying an unparsed opaque token via an OAuth 2.0 introspection endpoint (RFC 7662), the toolbox decodes the response into an introspectResp struct where the Active field is declared as a pointer to a boolean (*bool). The code only explicitly rejects a token if the response contains a populated active field set to false (if introspectResp.Active != nil &amp;amp;&amp;amp; !*introspectResp.Active). If an introspection endpoint responds with a payload that completely omits the mandatory active key, the internal variable remains nil, causing the conditional check to short-circuit. As a result, Toolbox accepts authorization tokens missing the &amp;#34;active&amp;#34; field, granting access to protected tools and underlying data sources.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.&lt;/p&gt;
&lt;p&gt;When verifying an unparsed opaque token via an OAuth 2.0 introspection endpoint (RFC 7662), the toolbox decodes the response into an introspectResp struct where the Active field is declared as a pointer to a boolean (*bool). The code only explicitly rejects a token if the response contains a populated active field set to false (if introspectResp.Active != nil &amp;amp;&amp;amp; !*introspectResp.Active). If an introspection endpoint responds with a payload that completely omits the mandatory active key, the internal variable remains nil, causing the conditional check to short-circuit. As a result, Toolbox accepts authorization tokens missing the &amp;#34;active&amp;#34; field, granting access to protected tools and underlying data sources.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-11717</guid>
    </item>
    <item>
      <title>GHSA-8fcc-w5hv-4gxv — googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaque…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8fcc-w5hv-4gxv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/googleapis/mcp-toolbox&lt;/p&gt;
&lt;p&gt;An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.&lt;/p&gt;
&lt;p&gt;When verifying an unparsed opaque token via an OAuth 2.0 introspection endpoint (RFC 7662), the toolbox decodes the response into an introspectResp struct where the Active field is declared as a pointer to a boolean (*bool). The code only explicitly rejects a token if the response contains a populated active field set to false (if introspectResp.Active != nil &amp;amp;&amp;amp; !*introspectResp.Active). If an introspection endpoint responds with a payload that completely omits the mandatory active key, the internal variable remains nil, causing the conditional check to short-circuit. As a result, Toolbox accepts authorization tokens missing the &amp;#34;active&amp;#34; field, granting access to protected tools and underlying data sources.&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;An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.&lt;/p&gt;
&lt;p&gt;When verifying an unparsed opaque token via an OAuth 2.0 introspection endpoint (RFC 7662), the toolbox decodes the response into an introspectResp struct where the Active field is declared as a pointer to a boolean (*bool). The code only explicitly rejects a token if the response contains a populated active field set to false (if introspectResp.Active != nil &amp;amp;&amp;amp; !*introspectResp.Active). If an introspection endpoint responds with a payload that completely omits the mandatory active key, the internal variable remains nil, causing the conditional check to short-circuit. As a result, Toolbox accepts authorization tokens missing the &amp;#34;active&amp;#34; field, granting access to protected tools and underlying data sources.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8fcc-w5hv-4gxv</guid>
    </item>
  </channel>
</rss>
