GitHub Advisoryadvisory · Go

GHSA-cwwm-hr97-qfxm SpiceDB checks involving relations with caveats can result in no permission when permission is expected

LOW Published 2025-06-06 Modified 2025-06-10 Official page ↗
Aliases
CVE-2025-49011
Ecosystem
Go
Packages
github.com/authzed/spicedb
Severity
Low
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Weaknesses
CWE-358
Reviewed
2025-06-06

Affected packages

• Go github.com/authzed/spicedb: < 1.44.2 → fixed in 1.44.2

Description

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: ``` definition user {} definition office { relation parent: office relation manager: user permission read = manager + parent->read } definition group { relation parent: office permission read = parent->read } definition document { relation owner: group with equals permission read = owner->read } caveat equals(actual string, required string) { actual == required } ``` and these relationships: ``` office:headoffice#manager@user:maria office:branch1#parent@office:headoffice group:admins#parent@office:branch1 group:managers#parent@office:headoffice document:budget#owner@group:admins[equals:{"required":"admin"}] document:budget#owner@group:managers[equals:{"required":"manager"}] ``` Permission for `'document:budget#read@user:maria with {"actual" : "admin"}'` is returned as NO_PERMISSION when HAS_PERMISSION is the correct answer. Patches Upgrade to v1.44.2. Workarounds Do not use caveats in your schema over an arrow’ed relation.

Related

Alias · CVE (1)

  • CVE-2025-49011 SpiceDB is an open source database for storing and querying fine-grained authorization data. vulnerability

Weakness · CWE (1)

  • CWE-358 Improperly Implemented Security Check for Standard weakness

References