<?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>Thu, 08 Oct 2026 02:55:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-252232</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-252232</link>
      <description>EUVD-2026-252232</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-252232</guid>
    </item>
    <item>
      <title>fkie_cve-2025-58373</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-58373</link>
      <description>&lt;p&gt;Roo Code is an AI-powered autonomous coding agent that lives in users&amp;#39; editors. Versions 3.25.23 and below contain a vulnerability where .rooignore protections could be bypassed using symlinks. This allows an attacker with write access to the workspace to trick the extension into reading files that were intended to be excluded. As a result, sensitive files such as .env or configuration files could be exposed. An attacker able to modify files within the workspace could gain unauthorized access to sensitive information by bypassing .rooignore rules. This could include secrets, configuration details, or other excluded project data. This is fixed in version 3.26.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Roo Code is an AI-powered autonomous coding agent that lives in users&amp;#39; editors. Versions 3.25.23 and below contain a vulnerability where .rooignore protections could be bypassed using symlinks. This allows an attacker with write access to the workspace to trick the extension into reading files that were intended to be excluded. As a result, sensitive files such as .env or configuration files could be exposed. An attacker able to modify files within the workspace could gain unauthorized access to sensitive information by bypassing .rooignore rules. This could include secrets, configuration details, or other excluded project data. This is fixed in version 3.26.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-58373</guid>
    </item>
  </channel>
</rss>
