<?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>Mon, 05 Oct 2026 22:47:11 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-252231</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-252231</link>
      <description>EUVD-2026-252231</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-252231</guid>
    </item>
    <item>
      <title>fkie_cve-2025-58372</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-58372</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 certain VS Code workspace configuration files (.code-workspace) are not protected in the same way as the .vscode folder. If the agent was configured to auto-approve file writes, an attacker able to influence prompts (for example via prompt injection) could cause malicious workspace settings or tasks to be written. These tasks could then be executed automatically when the workspace is reopened, resulting in arbitrary code execution. This issue 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 certain VS Code workspace configuration files (.code-workspace) are not protected in the same way as the .vscode folder. If the agent was configured to auto-approve file writes, an attacker able to influence prompts (for example via prompt injection) could cause malicious workspace settings or tasks to be written. These tasks could then be executed automatically when the workspace is reopened, resulting in arbitrary code execution. This issue is fixed in version 3.26.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-58372</guid>
    </item>
  </channel>
</rss>
