<?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:09:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-35412 — Directus has a TUS Upload Authorization Bypass Allows Arbitrary File Overwrite</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-35412</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; directus&lt;/p&gt;
&lt;p&gt;Directus is a real-time API and App dashboard for managing SQL database content. Prior to 11.16.1, Directus&amp;#39; TUS resumable upload endpoint (/files/tus) allows any authenticated user with basic file upload permissions to overwrite arbitrary existing files by UUID. The TUS controller performs only collection-level authorization checks, verifying the user has some permission on directus_files, but never validates item-level access to the specific file being replaced. As a result, row-level permission rules (e.g., &amp;#34;users can only update their own files&amp;#34;) are completely bypassed via the TUS path while being correctly enforced on the standard REST upload path. This vulnerability is fixed in 11.16.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; directus&lt;/p&gt;
&lt;p&gt;Directus is a real-time API and App dashboard for managing SQL database content. Prior to 11.16.1, Directus&amp;#39; TUS resumable upload endpoint (/files/tus) allows any authenticated user with basic file upload permissions to overwrite arbitrary existing files by UUID. The TUS controller performs only collection-level authorization checks, verifying the user has some permission on directus_files, but never validates item-level access to the specific file being replaced. As a result, row-level permission rules (e.g., &amp;#34;users can only update their own files&amp;#34;) are completely bypassed via the TUS path while being correctly enforced on the standard REST upload path. This vulnerability is fixed in 11.16.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-35412</guid>
    </item>
  </channel>
</rss>
