<?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 22:35:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-5043</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-5043</link>
      <description>EUVD-2026-5043</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-5043</guid>
    </item>
    <item>
      <title>fkie_cve-2024-32001</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-32001</link>
      <description>&lt;p&gt;SpiceDB is a graph database purpose-built for storing and evaluating access control data. Use of a relation of the form: `relation folder: folder | folder#parent` with an arrow such as `folder-&amp;gt;view` can cause LookupSubjects to only return the subjects found under subjects for either `folder` or `folder#parent`. This bug only manifests if the same subject type is used multiple types in a relation, relationships exist for both subject types and an arrow is used over the relation. Any user making a negative authorization decision based on the results of a LookupSubjects request with version before v1.30.1 is affected. Version 1.30.1 contains a patch for the issue. As a workaround, avoid using LookupSubjects for negative authorization decisions and/or avoid using the broken schema.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SpiceDB is a graph database purpose-built for storing and evaluating access control data. Use of a relation of the form: `relation folder: folder | folder#parent` with an arrow such as `folder-&amp;gt;view` can cause LookupSubjects to only return the subjects found under subjects for either `folder` or `folder#parent`. This bug only manifests if the same subject type is used multiple types in a relation, relationships exist for both subject types and an arrow is used over the relation. Any user making a negative authorization decision based on the results of a LookupSubjects request with version before v1.30.1 is affected. Version 1.30.1 contains a patch for the issue. As a workaround, avoid using LookupSubjects for negative authorization decisions and/or avoid using the broken schema.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-32001</guid>
    </item>
    <item>
      <title>GHSA-j85q-46hg-36p2 — SpiceDB: LookupSubjects may return partial results if a specific kind of relation is used</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-j85q-46hg-36p2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/authzed/spicedb&lt;/p&gt;
&lt;p&gt;### Background&lt;/p&gt;
&lt;p&gt;Use of a relation of the form: `relation folder: folder | folder#parent` with an arrow such as `folder-&amp;gt;view` can cause LookupSubjects to only return the subjects found under subjects for *either* `folder` or `folder#parent`.&lt;/p&gt;
&lt;p&gt;This bug *only* manifests if the *same* subject type is used multiple types in a relation, relationships exist for both subject types *and* an arrow is used over the relation.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Any user making a negative authorization decision based on the results of a LookupSubjects request with version before v1.30.1 is affected.&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using LookupSubjects for negative authorization decisions and/or avoid using the broken schema.&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;### Background&lt;/p&gt;
&lt;p&gt;Use of a relation of the form: `relation folder: folder | folder#parent` with an arrow such as `folder-&amp;gt;view` can cause LookupSubjects to only return the subjects found under subjects for *either* `folder` or `folder#parent`.&lt;/p&gt;
&lt;p&gt;This bug *only* manifests if the *same* subject type is used multiple types in a relation, relationships exist for both subject types *and* an arrow is used over the relation.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Any user making a negative authorization decision based on the results of a LookupSubjects request with version before v1.30.1 is affected.&lt;/p&gt;
&lt;p&gt;### Workarounds
Avoid using LookupSubjects for negative authorization decisions and/or avoid using the broken schema.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-j85q-46hg-36p2</guid>
    </item>
    <item>
      <title>gsd-2024-32001</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-32001</link>
      <description>gsd-2024-32001</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-32001</guid>
    </item>
  </channel>
</rss>
