<?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>Sat, 03 Oct 2026 20:05:50 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-199816</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-199816</link>
      <description>EUVD-2026-199816</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-199816</guid>
    </item>
    <item>
      <title>fkie_cve-2023-35930</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-35930</link>
      <description>&lt;p&gt;SpiceDB is an open source, Google Zanzibar-inspired, database system for creating and managing security-critical application permissions. Any user making a negative authorization decision based on the results of a `LookupResources` request with 1.22.0 is affected. For example, using `LookupResources` to find a list of resources to allow access to be okay: some subjects that should have access to a resource may not. But if using `LookupResources` to find a list of banned resources instead, then some users that shouldn&amp;#39;t have access may. Generally, `LookupResources` is not and should not be to gate access in this way - that&amp;#39;s what the `Check` API is for. Additionally, version 1.22.0 has included a warning about this bug since its initial release. Users are advised to upgrade to version 1.22.2. Users unable to upgrade should avoid using `LookupResources` for negative authorization decisions.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SpiceDB is an open source, Google Zanzibar-inspired, database system for creating and managing security-critical application permissions. Any user making a negative authorization decision based on the results of a `LookupResources` request with 1.22.0 is affected. For example, using `LookupResources` to find a list of resources to allow access to be okay: some subjects that should have access to a resource may not. But if using `LookupResources` to find a list of banned resources instead, then some users that shouldn&amp;#39;t have access may. Generally, `LookupResources` is not and should not be to gate access in this way - that&amp;#39;s what the `Check` API is for. Additionally, version 1.22.0 has included a warning about this bug since its initial release. Users are advised to upgrade to version 1.22.2. Users unable to upgrade should avoid using `LookupResources` for negative authorization decisions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-35930</guid>
    </item>
    <item>
      <title>GHSA-m54h-5x5f-5m6r — SpiceDB's LookupResources may return partial results</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m54h-5x5f-5m6r</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 a negative authorization decision based on the results of a LookupResources request with 1.22.0 is affected.&lt;/p&gt;
&lt;p&gt;For example, using `LookupResources` to find a list of resources to allow access to be okay: some subjects that should have access to a resource may not. But if using `LookupResources` to find a list of banned resources instead, then some users that shouldn&amp;#39;t have access may.&lt;/p&gt;
&lt;p&gt;Generally, `LookupResources` is not and should not be used to gate access in this way - that&amp;#39;s what the `Check` API is for. Additionally, version 1.22.0 has included a warning about this bug since its initial release.&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using `LookupResources` for negative authorization decisions if using `1.22.0`.&lt;/p&gt;
&lt;p&gt;### Patches
The only affected release is [v1.22.0](https://github.com/authzed/spicedb/releases/tag/v1.22.0), and it is patched in [v1.22.2](https://github.com/authzed/spicedb/releases/tag/v1.22.2) (there is no v1.22.1 release, though there is a git tag).&lt;/p&gt;
&lt;p&gt;### References
- https://github.com/authzed/spicedb/pull/1397&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 a negative authorization decision based on the results of a LookupResources request with 1.22.0 is affected.&lt;/p&gt;
&lt;p&gt;For example, using `LookupResources` to find a list of resources to allow access to be okay: some subjects that should have access to a resource may not. But if using `LookupResources` to find a list of banned resources instead, then some users that shouldn&amp;#39;t have access may.&lt;/p&gt;
&lt;p&gt;Generally, `LookupResources` is not and should not be used to gate access in this way - that&amp;#39;s what the `Check` API is for. Additionally, version 1.22.0 has included a warning about this bug since its initial release.&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using `LookupResources` for negative authorization decisions if using `1.22.0`.&lt;/p&gt;
&lt;p&gt;### Patches
The only affected release is [v1.22.0](https://github.com/authzed/spicedb/releases/tag/v1.22.0), and it is patched in [v1.22.2](https://github.com/authzed/spicedb/releases/tag/v1.22.2) (there is no v1.22.1 release, though there is a git tag).&lt;/p&gt;
&lt;p&gt;### References
- https://github.com/authzed/spicedb/pull/1397&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-m54h-5x5f-5m6r</guid>
    </item>
    <item>
      <title>gsd-2023-35930</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-35930</link>
      <description>gsd-2023-35930</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-35930</guid>
    </item>
  </channel>
</rss>
