CVE-2026-55866: SpiceDB: Checks involving relations with caveats can result in unconditional permission when conditional permission is expected
Impact Under concurrency, CheckPermission and CheckBulkPermissions can return PERMISSIONSHIPHASPERMISSION for a (resource, permission, subject) whose correct answer is PERMISSIONSHIPCONDITIONALPERMISSION. You are impacted if all of the following hold: 1. Your schema has a permission combining relations with an intersection or exclusion, where a subject reaches it through a caveated branch and a non-caveated branch.
Published Jun 19, 2026 · Updated Jun 23, 2026
Affected packages
github.com/authzed/spicedb
- Ecosystem
- Go
- Affected
- >= 1.34.0, < 1.54.0
- Fixed in
- 1.54.0
- Check
go list -m github.com/authzed/spicedb
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Under concurrency, CheckPermission and CheckBulkPermissions can return PERMISSIONSHIP_HAS_PERMISSION for a (resource, permission, subject) whose correct answer is PERMISSIONSHIP_CONDITIONAL_PERMISSION.
You are impacted if all of the following hold:
- Your schema has a permission combining relations with an intersection or exclusion, where a subject reaches it through a caveated branch and a non-caveated branch. For example:
definition user {}
caveat some_caveat(somecondition int) { somecondition == 42 }
definition document {
relation reader: user | user with some_caveat
relation writer: user
relation banned: user
permission has_permission = (reader & writer) - banned
}- A subject reaches the permission via the caveated edge:
document:firstdoc#reader@user:caveatedreader[some_caveat]
document:firstdoc#writer@user:caveatedreader- Your workload issues
LookupResourceswith acontextrequest parameter, concurrently withCheckPermission/CheckBulkPermissionsfor the same subject/resource, and - The dispatch result cache is enabled.
When all of the above are true, there is an intermittent window in which:
CheckPermission(document:firstdoc, has_permission, user:caveatedreader) → HAS_PERMISSION (incorrect; should be CONDITIONAL_PERMISSION)
CheckPermission(document:firstdoc, has_permission, user:caveatedreader, context = {"somecondition": 41}) → HAS_PERMISSION (incorrect; should be NO_PERMISSION)
Patches
v1.54.0
Workarounds
Disable the dispatch result cache (ClusterDispatchCacheConfig and DispatchCacheConfig)
Credited to ivanauth, miparnisari.
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-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-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
