<?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, 16 Nov 2026 22:57:19 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-407001</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-407001</link>
      <description>EUVD-2026-407001</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-407001</guid>
    </item>
    <item>
      <title>GHSA-7h45-q5jx-7r87 — Directus: Share update allows reassigning user_created and role</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7h45-q5jx-7r87</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: directus&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A non-admin user who can update their own shares can reassign a share&amp;#39;s creator (`user_created`), `role`, `item`, and `collection` fields after the share is created. The update is authorized against the row as it existed before the change, and the resulting row is never revalidated, so these fields can be set to values the user would not be permitted to assign when creating a share. By reassigning both `user_created` and `role` to an administrator the share&amp;#39;s effective permissions get elevated.&lt;/p&gt;
&lt;p&gt;This is a server-side authorization gap in the share update path. It does not by itself produce an administrator token. It re-opens a previously patched privilege-escalation surface on the effective permissions of a share.&lt;/p&gt;
&lt;p&gt;### Prerequisites&lt;/p&gt;
&lt;p&gt;- An authenticated non-admin account that holds update permission on `directus_shares`. This is not part of the baseline app-access grant, which is read-only on a user&amp;#39;s own shares, but it is part of the recommended defaults permission template for `directus_shares` that instances commonly apply so the share feature is usable.
- An item the account is allowed to share.
- Knowledge of an administrator user and role identifier to assign. In the reported case these were read from a relation on the shareable item using ordinary read permissions.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The recommended default permission for updating `directus_shares` selects rows where the caller is the creator and permits writes to the full field set, including the creator, role…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: directus&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A non-admin user who can update their own shares can reassign a share&amp;#39;s creator (`user_created`), `role`, `item`, and `collection` fields after the share is created. The update is authorized against the row as it existed before the change, and the resulting row is never revalidated, so these fields can be set to values the user would not be permitted to assign when creating a share. By reassigning both `user_created` and `role` to an administrator the share&amp;#39;s effective permissions get elevated.&lt;/p&gt;
&lt;p&gt;This is a server-side authorization gap in the share update path. It does not by itself produce an administrator token. It re-opens a previously patched privilege-escalation surface on the effective permissions of a share.&lt;/p&gt;
&lt;p&gt;### Prerequisites&lt;/p&gt;
&lt;p&gt;- An authenticated non-admin account that holds update permission on `directus_shares`. This is not part of the baseline app-access grant, which is read-only on a user&amp;#39;s own shares, but it is part of the recommended defaults permission template for `directus_shares` that instances commonly apply so the share feature is usable.
- An item the account is allowed to share.
- Knowledge of an administrator user and role identifier to assign. In the reported case these were read from a relation on the shareable item using ordinary read permissions.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The recommended default permission for updating `directus_shares` selects rows where the caller is the creator and permits writes to the full field set, including the creator, role…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7h45-q5jx-7r87</guid>
    </item>
  </channel>
</rss>
