CVE-2024-38361: SpiceDB exclusions can result in no permission returned when permission expected
Background Use of an exclusion under an arrow that has multiple resources may resolve to NOPERMISSION when permission is expected. For example, given this schema: 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…
Published Jun 20, 2024 · Updated Nov 18, 2024
Affected packages
github.com/authzed/spicedb
- Ecosystem
- Go
- Affected
- < 1.33.1
- Fixed in
- 1.33.1
- Check
go list -m github.com/authzed/spicedb
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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:
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
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-55866
SpiceDB: Checks involving relations with caveats can result in unconditional permission when conditional permission is expected
low3.7Jun 19, 2026CVE-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, 2025
