SpiceDB checks involving relations with caveats can result in no permission when permission is expected

Exploitation

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

CVSS

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

EPSS

• CVE-2025-49011: 0.33% estimated exploitation activity in the next 30 days; percentile 26.07 (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 On schemas involving arrows with caveats on the arrow’ed relation, when the path to resolve a CheckPermission request involves the evaluation of multiple caveated branches, requests may return a negative response when a positive response is expected. For example, given this schema: and these relationships: Permission for 'document:budget#read@user:maria with {"actual" : "admin"}' is returned as NOPERMISSION when HASPERMISSION is the correct answer. Patches Upgrade to v1.44.2. Workarounds Do not use caveats in your schema over an arrow’ed relation.

Published by the source

6 Jun 2025, 21:41 UTC

Last modified by the source

6 Jun 2025, 21:41 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cwwm-hr97-qfxm

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

# Patch Next advisory brief: CVE-2025-49011

Advisory: SpiceDB checks involving relations with caveats can result in no permission when permission is expected
IDs: CVE-2025-49011, GHSA-cwwm-hr97-qfxm
Record: https://patchnext.com/advisories/cve-2025-49011 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
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.44.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/authzed/spicedb: affected <= 1.44.0; fixed in 1.44.2

## 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-cwwm-hr97-qfxm (GitHub-reviewed advisory GHSA-cwwm-hr97-qfxm lists affected ranges: Go github.com/authzed/spicedb >=0 <=1.44.0)

Commands are suggestions: review each one before running it.