<?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 01:16:08 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-6252</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-6252</link>
      <description>EUVD-2026-6252</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-6252</guid>
    </item>
    <item>
      <title>fkie_cve-2024-39701</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-39701</link>
      <description>&lt;p&gt;Directus is a real-time API and App dashboard for managing SQL database content. Directus &amp;gt;=9.23.0, &amp;lt;=v10.5.3 improperly handles _in, _nin operators. It evaluates empty arrays as valid so expressions like {&amp;#34;role&amp;#34;: {&amp;#34;_in&amp;#34;: $CURRENT_USER.some_field}} would evaluate to true allowing the request to pass. This results in Broken Access Control because the rule fails to do what it was intended to do: Pass rule if **field** matches any of the **values**. This vulnerability is fixed in 10.6.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Directus is a real-time API and App dashboard for managing SQL database content. Directus &amp;gt;=9.23.0, &amp;lt;=v10.5.3 improperly handles _in, _nin operators. It evaluates empty arrays as valid so expressions like {&amp;#34;role&amp;#34;: {&amp;#34;_in&amp;#34;: $CURRENT_USER.some_field}} would evaluate to true allowing the request to pass. This results in Broken Access Control because the rule fails to do what it was intended to do: Pass rule if **field** matches any of the **values**. This vulnerability is fixed in 10.6.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-39701</guid>
    </item>
    <item>
      <title>GHSA-hxgm-ghmv-xjjm — Directus incorrectly handles `_in` filter</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hxgm-ghmv-xjjm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: directus&lt;/p&gt;
&lt;p&gt;### Summary
Directus &amp;gt;=9.23.0, &amp;lt;=v10.5.3 improperly handles _in, _nin operators.
It evaluates empty arrays as valid so expressions like {&amp;#34;role&amp;#34;: {&amp;#34;_in&amp;#34;: $CURRENT_USER.some_field}} would evaluate to true allowing the request to pass.&lt;/p&gt;
&lt;p&gt;### Details
This results in Broken Access Control because the rule fails to do what it was intended to do: Pass rule if **field** matches any of the **values**. ref: https://docs.directus.io/reference/filter-rules.html#filter-operators
In my example this would translate to &amp;#34;Pass rule if **&amp;lt;collection&amp;gt;.role** matches any of **[]**&amp;#34;. Which should fail. This instead passes in Directus &amp;lt;= v10.5.3, &amp;gt;=v9.23.0&lt;/p&gt;
&lt;p&gt;### PoC
{&amp;#34;role&amp;#34;: {&amp;#34;_in&amp;#34;: $CURRENT_USER.some_field}} field validation would pass if $CURRENT_USER.some_field is null.&lt;/p&gt;
&lt;p&gt;Real scenario: Using https://github.com/u12206050/directus-extension-role-chooser with the specified versions of Directus (I tested on 10.0.0) allows users with access to this feature set their role to whatever role if they don&amp;#39;t have any roles assigned (user_roles.role is left with the default value, null) despite the validation rule being 
```yaml
validation:
    role:
      _in: $CURRENT_USER.user_roles.role
```
Latest version of Directus (v10.8.3 and above) handles the above validation rule correctly.&lt;/p&gt;
&lt;p&gt;### Impact
Permissions fail to open for setups relying on this filter and can lead to users getting access to things they&amp;#39;re not supposed to.&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
Directus &amp;gt;=9.23.0, &amp;lt;=v10.5.3 improperly handles _in, _nin operators.
It evaluates empty arrays as valid so expressions like {&amp;#34;role&amp;#34;: {&amp;#34;_in&amp;#34;: $CURRENT_USER.some_field}} would evaluate to true allowing the request to pass.&lt;/p&gt;
&lt;p&gt;### Details
This results in Broken Access Control because the rule fails to do what it was intended to do: Pass rule if **field** matches any of the **values**. ref: https://docs.directus.io/reference/filter-rules.html#filter-operators
In my example this would translate to &amp;#34;Pass rule if **&amp;lt;collection&amp;gt;.role** matches any of **[]**&amp;#34;. Which should fail. This instead passes in Directus &amp;lt;= v10.5.3, &amp;gt;=v9.23.0&lt;/p&gt;
&lt;p&gt;### PoC
{&amp;#34;role&amp;#34;: {&amp;#34;_in&amp;#34;: $CURRENT_USER.some_field}} field validation would pass if $CURRENT_USER.some_field is null.&lt;/p&gt;
&lt;p&gt;Real scenario: Using https://github.com/u12206050/directus-extension-role-chooser with the specified versions of Directus (I tested on 10.0.0) allows users with access to this feature set their role to whatever role if they don&amp;#39;t have any roles assigned (user_roles.role is left with the default value, null) despite the validation rule being 
```yaml
validation:
    role:
      _in: $CURRENT_USER.user_roles.role
```
Latest version of Directus (v10.8.3 and above) handles the above validation rule correctly.&lt;/p&gt;
&lt;p&gt;### Impact
Permissions fail to open for setups relying on this filter and can lead to users getting access to things they&amp;#39;re not supposed to.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hxgm-ghmv-xjjm</guid>
    </item>
  </channel>
</rss>
