CVE-2025-64529: SpiceDB WriteRelationships fails silently if payload is too big
Impact 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 will 1.
Published Nov 13, 2025 · Updated May 14, 2026
Affected packages
github.com/authzed/spicedb
- Ecosystem
- Go
- Affected
- < 1.45.2
- Fixed in
- 1.45.2
- Check
go list -m github.com/authzed/spicedb
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Users who
- use the exclusion operator somewhere in their authorization schema
- have configured their SpiceDB server such that
--write-relationships-max-updates-per-callis bigger than 6500 - 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
WriteRelationshipscall, when in reality that call failed, - receive incorrect permission check results, if those relationships had to be read to resolve the relation involving the exclusion
Patches
Upgrade to v.145.2.
Workarounds
Set --write-relationships-max-updates-per-call to 1000.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-55866
SpiceDB: Checks involving relations with caveats can result in unconditional permission when conditional permission is expected
low3.7Jun 19, 2026CVE-2026-46668
SpiceDB: Caveat structures with nested lists can result in improper cache reuse
low2.3May 21, 2026CVE-2026-40091
SpiceDB's SPICEDB_DATASTORE_CONN_URI is leaked on startup logs
medium6.0Apr 14, 2026GHSA-vhvq-fv9f-wh4q
LookupResources Cursor section tampering can crash SpiceDB process via tuple.MustParse panic
low1.3Feb 6, 2026CVE-2025-65111
SpiceDB: LookupResources with Multiple Entrypoints across Different Definitions Can Return Incomplete Results
low2.9Nov 21, 2025CVE-2025-49011
SpiceDB checks involving relations with caveats can result in no permission when permission is expected
low3.7Jun 6, 2025
