<?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, 21 Oct 2026 09:12:27 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-194778</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-194778</link>
      <description>EUVD-2026-194778</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-194778</guid>
    </item>
    <item>
      <title>fkie_cve-2023-38503</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-38503</link>
      <description>&lt;p&gt;Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 10.3.0 and prior to version 10.5.0, the permission filters (i.e. `user_created IS $CURRENT_USER`) are not properly checked when using GraphQL subscription resulting in unauthorized users getting event on their subscription which they should not be receiving according to the permissions. This can be any collection but out-of-the box the `directus_users` collection is configured with such a permissions filter allowing you to get updates for other users when changes happen. Version 10.5.0 contains a patch. As a workaround, disable GraphQL subscriptions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Directus is a real-time API and App dashboard for managing SQL database content. Starting in version 10.3.0 and prior to version 10.5.0, the permission filters (i.e. `user_created IS $CURRENT_USER`) are not properly checked when using GraphQL subscription resulting in unauthorized users getting event on their subscription which they should not be receiving according to the permissions. This can be any collection but out-of-the box the `directus_users` collection is configured with such a permissions filter allowing you to get updates for other users when changes happen. Version 10.5.0 contains a patch. As a workaround, disable GraphQL subscriptions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-38503</guid>
    </item>
    <item>
      <title>GHSA-gggm-66rh-pp98 — Incorrect Permission Checking for GraphQL Subscriptions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-gggm-66rh-pp98</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;CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Access to information you should not have access to when the permissions rely on `$CURRENT_USER` for filtering.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The permission filters (i.e. `user_created IS $CURRENT_USER`) are not properly checked when using GraphQL subscription resulting in unauthorized users getting event on their subscription which they should not be receiving according to the permissions.
This can be any collection but out-of-the box the `directus_users` collection is configured with such a permissions filter allowing you to get updates for other users when changes happen.&lt;/p&gt;
&lt;p&gt;An example:
```graphql
subscription {
  directus_users_mutated {
    event
    data {
      id
      last_access
      last_page
    }
  }
}
```&lt;/p&gt;
&lt;p&gt;### Patches
https://github.com/directus/directus/pull/19155&lt;/p&gt;
&lt;p&gt;### Workarounds
Disable GraphQL Subscriptions&lt;/p&gt;
&lt;p&gt;### References&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;CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Access to information you should not have access to when the permissions rely on `$CURRENT_USER` for filtering.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The permission filters (i.e. `user_created IS $CURRENT_USER`) are not properly checked when using GraphQL subscription resulting in unauthorized users getting event on their subscription which they should not be receiving according to the permissions.
This can be any collection but out-of-the box the `directus_users` collection is configured with such a permissions filter allowing you to get updates for other users when changes happen.&lt;/p&gt;
&lt;p&gt;An example:
```graphql
subscription {
  directus_users_mutated {
    event
    data {
      id
      last_access
      last_page
    }
  }
}
```&lt;/p&gt;
&lt;p&gt;### Patches
https://github.com/directus/directus/pull/19155&lt;/p&gt;
&lt;p&gt;### Workarounds
Disable GraphQL Subscriptions&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-gggm-66rh-pp98</guid>
    </item>
    <item>
      <title>gsd-2023-38503</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-38503</link>
      <description>gsd-2023-38503</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-38503</guid>
    </item>
  </channel>
</rss>
