Most recent entries from all

bdu:2024-04839

EUVD-2026-5992

fkie_cve-2024-38361

Spicedb is an Open Source, Google Zanzibar-inspired permissions database to enable fine-grained authorization for customer applications. Use of an exclusion under an arrow that has multiple resources may resolve to `NO_PERMISSION` when permission is expected. If the resource exists under *multiple* folders and the user has access to view more than a single folder, SpiceDB may report the user does not have access due to a failure in the exclusion dispatcher to request that *all* the folders in which the user is a member be returned. Permission is returned as `NO_PERMISSION` when `PERMISSION` is expected on the `CheckPermission` API. This issue has been addressed in version 1.33.1. All users are advised to upgrade. There are no known workarounds for this issue.

GHSA-grjv-gjgr-66g2 — SpiceDB exclusions can result in no permission returned when permission expected

Affected: Go: github.com/authzed/spicedb

### Background

Use of an exclusion under an arrow that has multiple resources may resolve to `NO_PERMISSION` when permission is expected.

For example, given this schema:

```zed definition user {}

definition folder { relation member: user relation banned: user permission view = member - banned }

definition resource { relation folder: folder permission view = folder->view } ```

If the resource exists under *multiple* folders and the user has access to view more than a single folder, SpiceDB may report the user does not have access due to a failure in the exclusion dispatcher to request that *all* the folders in which the user is a member be returned

### Impact

Permission is returned as `NO_PERMISSION` when `PERMISSION` is expected on the `CheckPermission` API.

### Workarounds

None