Lookup operations do not take into account wildcards in SpiceDB

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2022-21646: 1.28% estimated exploitation activity in the next 30 days; percentile 70.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Any user making use of a wildcard relationship under the right hand branch of an exclusion or within an intersection operation will see Lookup/LookupResources return a resource as "accessible" if it is not accessible by virtue of the inclusion of the wildcard in the intersection or the right side of the exclusion. For example, given schema: If user: is placed into the banned relation for a particular resource, view should return false for all resources. in v1.3.0, the wildcard is ignored entirely in lookup's dispatch, resulting in the banned wildcard being ignored in the exclusion. Workarounds Don't make use of wildcards on the right side of intersections or within exclusions. References https://github.com/authzed/spicedb/issues/358 For more information If you have any questions or comments about this advisory: Open an issue in SpiceDB Ask a question in the SpiceDB Discord

Published by the source

13 Jan 2022, 15:05 UTC

Last modified by the source

3 Feb 2023, 05:04 UTC

Source last checked

26 Oct 2026, 14:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7p8f-8hjm-wm92

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-21646

Advisory: Lookup operations do not take into account wildcards in SpiceDB
IDs: CVE-2022-21646, GHSA-7p8f-8hjm-wm92
Record: https://patchnext.com/advisories/cve-2022-21646 (revision 1, source checked 26 Oct 2026, 14:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/authzed/spicedb 1.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/authzed/spicedb: affected >= 1.3.0, <= 1.3.0; fixed in 1.4.0

## Suggested inspection (read-only)
- Go github.com/authzed/spicedb: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/authzed/spicedb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7p8f-8hjm-wm92 (GitHub-reviewed advisory GHSA-7p8f-8hjm-wm92 lists affected ranges: Go github.com/authzed/spicedb >=1.3.0 <=1.3.0)

Commands are suggestions: review each one before running it.