CVE-2026-46668: SpiceDB: Caveat structures with nested lists can result in improper cache reuse
Impact Users are impacted if: - They have a caveat structure with a nested list, e.g.: - Their system exercises that caveat with either CheckBulkPermission or else LookupResources running with the --experimental-lookup-resources-version flag set to lr3, implying they are using the experimental version 3 of LookupResources - An attacker can cause the system to craft a request to SpiceDB where either: 1.
Published May 21, 2026 · Updated Jun 11, 2026
Affected packages
github.com/authzed/spicedb
- Ecosystem
- Go
- Affected
- >= 1.15.0, < 1.52.0
- Fixed in
- 1.52.0
- Check
go list -m github.com/authzed/spicedb
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Users are impacted if:
- They have a caveat structure with a nested list, e.g.:
caveat shape(x list<any>) {
x == [["a"], "b"]
}- Their system exercises that caveat with either CheckBulkPermission or else LookupResources running with the
--experimental-lookup-resources-versionflag set tolr3, implying they are using the experimental version 3 ofLookupResources - An attacker can cause the system to craft a request to SpiceDB where either:
- It's a
CheckBulkrequest where there are two check items that are identical except for their combined caveat context, and one of the caveat contexts evaluates positively and the other evaluates negatively - It's a
LookupResourcesrequest where two resources have the same evaluation contents except for their caveat context, and one would evaluate positively and the other would evaluate negatively
If all of the above are true, it would be possible for SpiceDB to erroneously return that a user has access to a resource that they do not have access to.
Patches
This problem was addressed in https://github.com/authzed/spicedb/pull/3065 and released in version v1.52.0.
Workarounds
If using v3 of LookupResources, turn the flag off.
If possible, refactor the caveat declaration structure so that it does not operate on a list of lists, but rather any other composite structure.
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-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-64529
SpiceDB WriteRelationships fails silently if payload is too big
low6.5Nov 13, 2025CVE-2025-49011
SpiceDB checks involving relations with caveats can result in no permission when permission is expected
low3.7Jun 6, 2025
