<?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>Tue, 06 Oct 2026 17:23:03 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-260634</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-260634</link>
      <description>EUVD-2026-260634</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-260634</guid>
    </item>
    <item>
      <title>fkie_cve-2025-64529</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-64529</link>
      <description>&lt;p&gt;SpiceDB is an open source database system for creating and managing security-critical application permissions. In versions prior to 1.45.2, users who use the exclusion operator somewhere in their authorization schema; have configured their SpiceDB server such that `--write-relationships-max-updates-per-call` is bigger than 6500; and issue calls to WriteRelationships with a large enough number of updates that cause the payload to be bigger than what their datastore allows; will receive a successful response from their `WriteRelationships` call, when in reality that call failed, and receive incorrect permission check results, if those relationships had to be read to resolve the relation involving the exclusion. Version 1.45.2 contains a patch for the issue. As a workaround, set `--write-relationships-max-updates-per-call` to `1000`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SpiceDB is an open source database system for creating and managing security-critical application permissions. In versions prior to 1.45.2, users who use the exclusion operator somewhere in their authorization schema; have configured their SpiceDB server such that `--write-relationships-max-updates-per-call` is bigger than 6500; and issue calls to WriteRelationships with a large enough number of updates that cause the payload to be bigger than what their datastore allows; will receive a successful response from their `WriteRelationships` call, when in reality that call failed, and receive incorrect permission check results, if those relationships had to be read to resolve the relation involving the exclusion. Version 1.45.2 contains a patch for the issue. As a workaround, set `--write-relationships-max-updates-per-call` to `1000`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-64529</guid>
    </item>
    <item>
      <title>GHSA-pm3x-jrhh-qcr7 — SpiceDB WriteRelationships fails silently if payload is too big</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pm3x-jrhh-qcr7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/authzed/spicedb&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Users who 
1. use the exclusion operator somewhere in their authorization schema
1. have configured their SpiceDB server such that `--write-relationships-max-updates-per-call` is bigger than 6500
1. issue calls to WriteRelationships with a large enough number of updates that cause the payload to be bigger than what their datastore allows&lt;/p&gt;
&lt;p&gt;will&lt;/p&gt;
&lt;p&gt;1. receive a successful response from their `WriteRelationships` call, when in reality that call failed,
2. receive incorrect permission check results, if those relationships had to be read to resolve the relation involving the exclusion&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Upgrade to v.145.2.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Set `--write-relationships-max-updates-per-call` to `1000`.&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&lt;/p&gt;
&lt;p&gt;Users who 
1. use the exclusion operator somewhere in their authorization schema
1. have configured their SpiceDB server such that `--write-relationships-max-updates-per-call` is bigger than 6500
1. issue calls to WriteRelationships with a large enough number of updates that cause the payload to be bigger than what their datastore allows&lt;/p&gt;
&lt;p&gt;will&lt;/p&gt;
&lt;p&gt;1. receive a successful response from their `WriteRelationships` call, when in reality that call failed,
2. receive incorrect permission check results, if those relationships had to be read to resolve the relation involving the exclusion&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Upgrade to v.145.2.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Set `--write-relationships-max-updates-per-call` to `1000`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pm3x-jrhh-qcr7</guid>
    </item>
  </channel>
</rss>
