<?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://db.gcve.eu</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>Fri, 30 Oct 2026 13:59:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-115413 — AWS API MCP Server OAuth Token Audience Validation Bypass</title>
      <link>https://db.gcve.eu/vuln/cve-2026-115413</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; aws-api-mcp-server&lt;/p&gt;
&lt;p&gt;Missing token audience validation in the OAuth authentication mode of AWS API MCP Server before version 1.6.0 might allow local users to run AWS operations with the server&amp;#39;s configured AWS credentials via an access token issued to another application by the same identity provider.&lt;/p&gt;
&lt;p&gt;To remediate this issue, users should upgrade to version 1.6.0 and configure the expected token audience or client ID for the server.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; aws-api-mcp-server&lt;/p&gt;
&lt;p&gt;Missing token audience validation in the OAuth authentication mode of AWS API MCP Server before version 1.6.0 might allow local users to run AWS operations with the server&amp;#39;s configured AWS credentials via an access token issued to another application by the same identity provider.&lt;/p&gt;
&lt;p&gt;To remediate this issue, users should upgrade to version 1.6.0 and configure the expected token audience or client ID for the server.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-115413</guid>
    </item>
  </channel>
</rss>
