CVE-2025-64529
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-11-10

Last updated on: 2025-11-21

Assigner: GitHub, Inc.

Description
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`.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-11-10
Last Modified
2025-11-21
Generated
2026-05-07
AI Q&A
2025-11-11
EPSS Evaluated
2026-05-05
NVD
CVE-2025-64529
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
authzed spicedb to 1.45.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in SpiceDB versions prior to 1.45.2 occurs when users employ the exclusion operator in their authorization schema, configure the server with a write-relationships-max-updates-per-call value greater than 6500, and issue WriteRelationships calls with a payload larger than the datastore allows. In such cases, the WriteRelationships call returns a successful response even though it actually failed, leading to incorrect permission check results when those relationships are read to resolve relations involving the exclusion operator. Version 1.45.2 fixes this issue, and a workaround is to set the write-relationships-max-updates-per-call to 1000.


How can this vulnerability impact me? :

This vulnerability can cause your application to receive incorrect permission check results because failed WriteRelationships calls are reported as successful. This means unauthorized access might be granted or legitimate access denied, potentially compromising the security of your application permissions and leading to security risks.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability immediately, either upgrade SpiceDB to version 1.45.2 or later, which contains the patch for this issue, or as a workaround, set the server configuration parameter `--write-relationships-max-updates-per-call` to 1000 to avoid triggering the bug.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart