# SpiceDB: Checks involving relations with caveats can result in unconditional permission when conditional permission is expected

Advisory record · `GHSA-4vrg-r928-h5vv`

- **Identifiers:** `GHSA-4vrg-r928-h5vv` · `CVE-2026-55866` · `GO-2026-5133`
- **State:** Confirmed
- **Severity:** CVSS 3.7 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 19 Jun 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 Jun 2026, 21:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/authzed/spicedb` (Go): affected `>=1.34.0, <1.54.0`; fixed in `1.54.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> SpiceDB versions from 1.34.0 before 1.54.0 can return HAS_PERMISSION instead of CONDITIONAL_PERMISSION from CheckPermission and CheckBulkPermissions, under specific conditions. The issue requires a schema that combines a caveated branch and a non-caveated branch in a permission, concurrent LookupResources calls with a context parameter, and the dispatch result cache enabled. Upgrade to 1.54.0. As a workaround, disable the dispatch result cache.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 3.7 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0034, the 28th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:07 UTC: First seen by agentprime
- 31 Oct 2026, 15:07 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4vrg-r928-h5vv)

## Sources

- [GitHub Advisory Database: GHSA-4vrg-r928-h5vv](https://github.com/advisories/GHSA-4vrg-r928-h5vv)
- [OSV: GHSA-4vrg-r928-h5vv](https://osv.dev/vulnerability/GHSA-4vrg-r928-h5vv)
- <https://github.com/authzed/spicedb/security/advisories/GHSA-4vrg-r928-h5vv>
- <https://github.com/authzed/spicedb>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4vrg-r928-h5vv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4vrg-r928-h5vv/>. Everything for agents: <https://agentprime.io/llms.txt>.
