CVE-2026-55866

published 14 Sep 2026 · updated 14 Sep 2026

SpiceDBChecks involving relations with caveats can result in unconditional permission when conditional permission is expected

3.7LowCVSS 3.7EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
authzed>=1.34.1 <1.54.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-55866 severity on Zeptric[![CVE-2026-55866](https://zeptric.io/badge/cve/CVE-2026-55866.svg)](https://zeptric.io/cve/CVE-2026-55866)