CVE-2026-46668

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.

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.

Kodem intelligence

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

1. What is CVE-2026-46668? CVE-2026-46668 is a low-severity security vulnerability in github.com/authzed/spicedb (go), affecting versions >= 1.15.0, < 1.52.0. It is fixed in 1.52.0.
2. Which versions of github.com/authzed/spicedb are affected by CVE-2026-46668? github.com/authzed/spicedb (go) versions >= 1.15.0, < 1.52.0 is affected.
3. Is there a fix for CVE-2026-46668? Yes. CVE-2026-46668 is fixed in 1.52.0. Upgrade to this version or later.
4. Is CVE-2026-46668 exploitable, and should I be worried? Whether CVE-2026-46668 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-46668 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-46668? Upgrade github.com/authzed/spicedb to 1.52.0 or later.