<?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>Tue, 06 Oct 2026 10:23:43 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-366477</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-366477</link>
      <description>EUVD-2026-366477</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-366477</guid>
    </item>
    <item>
      <title>fkie_cve-2026-87913</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-87913</link>
      <description>&lt;p&gt;A missing S3 bucket ownership verification in the AWS Security Agent MCP server before 0.2.0 version might allow remote attackers to obtain the private source archive of a scanned workspace, including credentials and infrastructure state contained in that archive, via a pre-registered storage bucket whose name is derived from a publicly known account identifier.&lt;/p&gt;
&lt;p&gt;To remediate this issue, users should upgrade to version 0.2.0. Users should also verify that the scan output bucket in their account is owned by their own account, because upgrading does not release a bucket name that a third party has already registered.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A missing S3 bucket ownership verification in the AWS Security Agent MCP server before 0.2.0 version might allow remote attackers to obtain the private source archive of a scanned workspace, including credentials and infrastructure state contained in that archive, via a pre-registered storage bucket whose name is derived from a publicly known account identifier.&lt;/p&gt;
&lt;p&gt;To remediate this issue, users should upgrade to version 0.2.0. Users should also verify that the scan output bucket in their account is owned by their own account, because upgrading does not release a bucket name that a third party has already registered.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-87913</guid>
    </item>
  </channel>
</rss>
