<?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, 14 Oct 2026 23:58:15 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-356515</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-356515</link>
      <description>EUVD-2026-356515</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-356515</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53457</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53457</link>
      <description>&lt;p&gt;Blueprint Studio is a VS Code-like file editor for Home Assistant configuration files. Prior to 2.5.2, the legacy stateless terminal command execution path in custom_components/blueprint_studio/backend/terminal_manager.py accepted a cwd working-directory parameter and checked only whether the directory existed, without requiring it to remain inside the Home Assistant configuration directory. An administrator using the restricted terminal helper could select an existing directory outside the intended configuration boundary. Commands could then access or modify host paths permitted by the Home Assistant container and filesystem permissions, weakening the helper&amp;#39;s expected filesystem restriction. This issue is fixed in version 2.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Blueprint Studio is a VS Code-like file editor for Home Assistant configuration files. Prior to 2.5.2, the legacy stateless terminal command execution path in custom_components/blueprint_studio/backend/terminal_manager.py accepted a cwd working-directory parameter and checked only whether the directory existed, without requiring it to remain inside the Home Assistant configuration directory. An administrator using the restricted terminal helper could select an existing directory outside the intended configuration boundary. Commands could then access or modify host paths permitted by the Home Assistant container and filesystem permissions, weakening the helper&amp;#39;s expected filesystem restriction. This issue is fixed in version 2.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53457</guid>
    </item>
  </channel>
</rss>
