<?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 04:56:11 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-291947</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-291947</link>
      <description>EUVD-2026-291947</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-291947</guid>
    </item>
    <item>
      <title>fkie_cve-2026-40196</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-40196</link>
      <description>&lt;p&gt;HomeBox is a home inventory and organization system. Versions prior to 0.25.0 contain a vulnerability where the defaultGroup ID remained permanently assigned to a user after being invited to a group, even after their access to that group was revoked. While the web interface correctly enforced the access revocation and prevented the user from viewing or modifying the group&amp;#39;s contents, the API did not. Because the original group ID persisted as the user&amp;#39;s defaultGroup, and this value was not properly validated when the X-Tenant header was omitted, the user could still perform full CRUD operations on the group&amp;#39;s collections through the API, bypassing the intended access controls. This issue has been fixed in version 0.25.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;HomeBox is a home inventory and organization system. Versions prior to 0.25.0 contain a vulnerability where the defaultGroup ID remained permanently assigned to a user after being invited to a group, even after their access to that group was revoked. While the web interface correctly enforced the access revocation and prevented the user from viewing or modifying the group&amp;#39;s contents, the API did not. Because the original group ID persisted as the user&amp;#39;s defaultGroup, and this value was not properly validated when the X-Tenant header was omitted, the user could still perform full CRUD operations on the group&amp;#39;s collections through the API, bypassing the intended access controls. This issue has been fixed in version 0.25.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-40196</guid>
    </item>
  </channel>
</rss>
