Advisory

GHSA-cwwm-hr97-qfxm

Also known as: CVE-2025-49011, GO-2025-3744

Summary

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

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2025-06-06 21:41 UTC
Modified
2025-06-10 19:58 UTC

Affected packages and fixes

github.com/authzed/spicedb

Go · All systems

Affected

  • introduced 0, fixed 1.44.2 (semver)

Fixed versions

1.44.2

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences