Skip to content

CVE-2026-55866 SpiceDBChecks involving relations with caveats can result in unconditional permission when conditional permission is expected

LowCVSS 3.7 EPSS 0.34%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

Description

SpiceDB is an open source database system for creating and managing security-critical application permissions. From 1.34.0 until 1.54.0, SpiceDB can return PERMISSIONSHIP_HAS_PERMISSION instead of PERMISSIONSHIP_CONDITIONAL_PERMISSION or PERMISSIONSHIP_NO_PERMISSION because checkRequestToKey() and checkRequestToKeyWithCanonical() in internal/dispatch/keys/computed.go omit CheckHints when constructing dispatch Check cache keys. The incorrect result requires a permission combining relations with intersection or exclusion, a subject reachable through caveated and non-caveated branches, LookupResources with a context parameter running concurrently with CheckPermission or CheckBulkPermissions for the same resource and subject, and an enabled dispatch result cache. Under these conditions, a result computed for one hint set can poison the cache entry used by a semantically different authorization check, allowing permission without satisfying the caveat. This issue is fixed in version 1.54.0.

Upgrade path

2 packages: 1 fixed.

PackageAffectedFixed inStatus
authzed github.com/authzed/spicedb(Go) >= 1.34.0, < 1.54.0 1.54.0 Fixed
authzed github.com/authzed/spicedb = >= 1.34.1, < 1.54.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
authzed github.com/authzed/spicedb(Go) >= 1.34.0, < 1.54.0 1.54.0
authzed github.com/authzed/spicedb = >= 1.34.1, < 1.54.0 No fix listed

References