<?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>Sun, 04 Oct 2026 06:14:14 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-234525</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-234525</link>
      <description>EUVD-2026-234525</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-234525</guid>
    </item>
    <item>
      <title>fkie_cve-2022-21646</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-21646</link>
      <description>&lt;p&gt;SpiceDB is a database system for managing security-critical application permissions. Any user making use of a wildcard relationship under the right hand branch of an `exclusion` or within an `intersection` operation will see `Lookup`/`LookupResources` return a resource as &amp;#34;accessible&amp;#34; if it is *not* accessible by virtue of the inclusion of the wildcard in the intersection or the right side of the exclusion. In `v1.3.0`, the wildcard is ignored entirely in lookup&amp;#39;s dispatch, resulting in the `banned` wildcard being ignored in the exclusion. Version 1.4.0 contains a patch for this issue. As a workaround, don&amp;#39;t make use of wildcards on the right side of intersections or within exclusions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SpiceDB is a database system for managing security-critical application permissions. Any user making use of a wildcard relationship under the right hand branch of an `exclusion` or within an `intersection` operation will see `Lookup`/`LookupResources` return a resource as &amp;#34;accessible&amp;#34; if it is *not* accessible by virtue of the inclusion of the wildcard in the intersection or the right side of the exclusion. In `v1.3.0`, the wildcard is ignored entirely in lookup&amp;#39;s dispatch, resulting in the `banned` wildcard being ignored in the exclusion. Version 1.4.0 contains a patch for this issue. As a workaround, don&amp;#39;t make use of wildcards on the right side of intersections or within exclusions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-21646</guid>
    </item>
    <item>
      <title>GHSA-7p8f-8hjm-wm92 — Lookup operations do not take into account wildcards in SpiceDB</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7p8f-8hjm-wm92</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/authzed/spicedb&lt;/p&gt;
&lt;p&gt;### Impact
Any user making use of a wildcard relationship under the right hand branch of an `exclusion` or within an `intersection` operation will see `Lookup`/`LookupResources` return a resource as &amp;#34;accessible&amp;#34; if it is *not* accessible by virtue of the inclusion of the wildcard in the intersection or the right side of the exclusion.&lt;/p&gt;
&lt;p&gt;For example, given schema:&lt;/p&gt;
&lt;p&gt;```zed
definition user {}&lt;/p&gt;
&lt;p&gt;definition resource {
   relation viewer: user
   relation banned: user | user:*
   permission view = viewer - banned
}
```&lt;/p&gt;
&lt;p&gt;If `user:*` is placed into the `banned` relation for a particular resource, `view` should return false for *all* resources. in `v1.3.0`, the wildcard is ignored entirely in lookup&amp;#39;s dispatch, resulting in the `banned` wildcard being ignored in the exclusion.&lt;/p&gt;
&lt;p&gt;### Workarounds
Don&amp;#39;t make use of wildcards on the right side of intersections or within exclusions.&lt;/p&gt;
&lt;p&gt;### References
https://github.com/authzed/spicedb/issues/358&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in [SpiceDB](https://github.com/authzed/spicedb)
* Ask a question in the [SpiceDB Discord](https://authzed.com/discord)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/authzed/spicedb&lt;/p&gt;
&lt;p&gt;### Impact
Any user making use of a wildcard relationship under the right hand branch of an `exclusion` or within an `intersection` operation will see `Lookup`/`LookupResources` return a resource as &amp;#34;accessible&amp;#34; if it is *not* accessible by virtue of the inclusion of the wildcard in the intersection or the right side of the exclusion.&lt;/p&gt;
&lt;p&gt;For example, given schema:&lt;/p&gt;
&lt;p&gt;```zed
definition user {}&lt;/p&gt;
&lt;p&gt;definition resource {
   relation viewer: user
   relation banned: user | user:*
   permission view = viewer - banned
}
```&lt;/p&gt;
&lt;p&gt;If `user:*` is placed into the `banned` relation for a particular resource, `view` should return false for *all* resources. in `v1.3.0`, the wildcard is ignored entirely in lookup&amp;#39;s dispatch, resulting in the `banned` wildcard being ignored in the exclusion.&lt;/p&gt;
&lt;p&gt;### Workarounds
Don&amp;#39;t make use of wildcards on the right side of intersections or within exclusions.&lt;/p&gt;
&lt;p&gt;### References
https://github.com/authzed/spicedb/issues/358&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in [SpiceDB](https://github.com/authzed/spicedb)
* Ask a question in the [SpiceDB Discord](https://authzed.com/discord)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7p8f-8hjm-wm92</guid>
    </item>
    <item>
      <title>gsd-2022-21646</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-21646</link>
      <description>gsd-2022-21646</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-21646</guid>
    </item>
  </channel>
</rss>
