github.com/authzed/spicedb
Affected
- introduced
1.34.0, fixed1.54.0(semver)
Fixed versions
1.54.0
Fix
- Fixed version
1.54.0go get github.com/authzed/[email protected]
Advisory
Also known as: CVE-2026-55866, GO-2026-5133
SpiceDB: Checks involving relations with caveats can result in unconditional permission when conditional permission is expected
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:
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
}
document:firstdoc#reader@user:caveatedreader[some_caveat]
document:firstdoc#writer@user:caveatedreader
LookupResources with a context request parameter, concurrently with CheckPermission/CheckBulkPermissions for the same subject/resource, andWhen 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)
Low Basis: The source's own band: LOW
1.34.0, fixed 1.54.0 (semver)1.54.0
1.54.0go get github.com/authzed/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0