LowGHSA-mqcf-gqvg-rmhmCVE-2026-46668GO-2026-5514

SpiceDB: Caveat structures with nested lists can result in improper cache reuse

Published 21 May 2026 · Updated 25 Jun 2026

Is your project on an affected github.com/authzed/spicedb?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=1.15.0 <1.52.0
Fixed in
1.52.0
Update to the fixed version for your release line, for example:go get github.com/authzed/spicedb@v1.52.0

Details

Impact

Users are impacted if:

  • They have a caveat structure with a nested list, e.g.:
  caveat shape(x list<any>) {
    x == [["a"], "b"]
  }
  • Their system exercises that caveat with either CheckBulkPermission or else LookupResources running with the --experimental-lookup-resources-version flag set to lr3, implying they are using the experimental version 3 of LookupResources
  • An attacker can cause the system to craft a request to SpiceDB where either: 1. It's a CheckBulk request where there are two check items that are identical except for their combined caveat context, and one of the caveat contexts evaluates positively and the other evaluates negatively 2. It's a LookupResources request where two resources have the same evaluation contents except for their caveat context, and one would evaluate positively and the other would evaluate negatively

If all of the above are true, it would be possible for SpiceDB to erroneously return that a user has access to a resource that they do not have access to.

Patches

This problem was addressed in https://github.com/authzed/spicedb/pull/3065 and released in version v1.52.0.

Workarounds

If using v3 of LookupResources, turn the flag off.

If possible, refactor the caveat declaration structure so that it does not operate on a list of lists, but rather any other composite structure.

Is GHSA-mqcf-gqvg-rmhm in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/authzed/spicedb, and gives you the command that fixes it.

More advisories for github.com/authzed/spicedb

  • LowCVE-2026-40091SpiceDB's SPICEDB_DATASTORE_CONN_URI is leaked on startup logs in github.com/authzed/spicedb · 25 Jun 2026
  • LowCVE-2026-55866SpiceDB: Checks involving relations with caveats can result in unconditional permission when conditional permission is expected in github.com/authzed/spicedb · 25 Jun 2026
  • LowCVE-2026-55866SpiceDB: Checks involving relations with caveats can result in unconditional permission when conditional permission is expected · 19 Jun 2026
  • MediumCVE-2026-40091SpiceDB's SPICEDB_DATASTORE_CONN_URI is leaked on startup logs · 14 Apr 2026
  • LowGO-2026-4465LookupResources Cursor section tampering can crash SpiceDB process via tuple.MustParse panic in github.com/authzed/spicedb · 17 Feb 2026
  • LowGHSA-vhvq-fv9f-wh4qLookupResources Cursor section tampering can crash SpiceDB process via tuple.MustParse panic · 6 Feb 2026
All 31 advisories for github.com/authzed/spicedb

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.